From: Derek Johansen <djohanse678@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Build errors with latest commit
Date: Sat, 8 Apr 2017 22:28:04 -0600 [thread overview]
Message-ID: <CAOv0vd=-w4+fFjPPrDXgwf5-_ehvHJHW8-AJV7=WO68NY07JrA@mail.gmail.com> (raw)
After pulling in the latest commit, running sudo ./build.sh errors out
as shown below:
bcc -0 -O -I/home/djohanse/elk2/elks/elks/include
-DELKS_VERSION_CODE=0x00020000 -DUTS_RELEASE=\"0.2.0\" -D__KERNEL__
-ansi -c -o chqueue.o chqueue.c
/home/djohanse/elk2/elks/elks/include/linuxmt/fs.h:252.33: error:
undefined structure
/home/djohanse/elk2/elks/elks/include/linuxmt/fs.h:302.31: error:
undefined structure
make[3]: *** [super.o] Error 1
make[3]: Leaving directory `/home/djohanse/elk2/elks/elks/fs'
make[2]: *** [fs/fs.a] Error 2
make[2]: *** Waiting for unfinished jobs....
bcc -0 -O -I/home/djohanse/elk2/elks/elks/include
-DELKS_VERSION_CODE=0x00020000 -DUTS_RELEASE=\"0.2.0\" -D__KERNEL__
-ansi -c -o string.o string.c
/home/djohanse/elk2/elks/elks/include/linuxmt/fs.h:252.33: error:
undefined structure
/home/djohanse/elk2/elks/elks/include/linuxmt/fs.h:302.31: error:
undefined structure
make[3]: *** [chqueue.o] Error 1
make[3]: Leaving directory `/home/djohanse/elk2/elks/elks/lib'
make[2]: *** [lib/lib.a] Error 2
make[2]: Leaving directory `/home/djohanse/elk2/elks/elks'
make[1]: *** [Image] Error 2
make[1]: Leaving directory `/home/djohanse/elk2/elks/elks'
make: *** [elks] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
Build script has terminated with error 4
djohanse@djohanse-VirtualBox:~/elk2/elks$
next reply other threads:[~2017-04-09 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 4:28 Derek Johansen [this message]
2017-04-09 6:13 ` Build errors with latest commit Derek Johansen
2017-04-09 12:52 ` Build errors with latest commit which added FAT file system support to ELKS Georg Potthast 2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOv0vd=-w4+fFjPPrDXgwf5-_ehvHJHW8-AJV7=WO68NY07JrA@mail.gmail.com' \
--to=djohanse678@gmail.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).