From: Nicholas Kinar <n.kinar@usask.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Updated status on the compilation of busybox on Mac OS X
Date: Wed, 02 Dec 2009 16:55:16 -0600 [thread overview]
Message-ID: <4B16F054.8070104@usask.ca> (raw)
In-Reply-To: <4B16EECC.4090909@usask.ca>
Hello--
I've now added these entries to the Buildroot .config file:
BR2_ENABLE_LOCALE=no
BR2_BUILD_SUFFIX=apple-darwin9
BR2_EXTRA_GCC_CONFIG_OPTIONS="--host=i686-apple-darwin9
--build=i686-apple-darwin9"
Buildroot continues to build, but crashes with the following error. (My
apologies for the odd characters in the error posting.) Apparently the
compiler cannot find elf.h, which is required for compilation. This
could prove to be a real show-stopper, since elf.h does not appear to be
included with BSD-style systems.
lsmod.c:28:24: error: asm/unistd.h: No such file or directory
insmod.c:29:24: error: asm/unistd.h: No such file or directory
make[1]: *** [lsmod.o] Error 1
make[1]: *** Waiting for unfinished jobs....
modprobe.c:35:17: error: elf.h: No such file or directory
modprobe.c:38:24: error: asm/unistd.h: No such file or directory
make[1]: *** [insmod.o] Error 1
modprobe.c: In function ?get_section32?:
modprobe.c:437: error: ?Elf32_Ehdr? undeclared (first use in this function)
modprobe.c:437: error: (Each undeclared identifier is reported only once
modprobe.c:437: error: for each function it appears in.)
modprobe.c:437: error: ?hdr? undeclared (first use in this function)
modprobe.c:438: error: ?Elf32_Shdr? undeclared (first use in this function)
modprobe.c:438: error: ?sechdrs? undeclared (first use in this function)
modprobe.c: In function ?get_section64?:
modprobe.c:464: error: ?Elf64_Ehdr? undeclared (first use in this function)
modprobe.c:464: error: ?hdr? undeclared (first use in this function)
modprobe.c:465: error: ?Elf64_Shdr? undeclared (first use in this function)
modprobe.c:465: error: ?sechdrs? undeclared (first use in this function)
modprobe.c: In function ?elf_ident?:
modprobe.c:491: error: ?EI_CLASS? undeclared (first use in this function)
modprobe.c:491: error: ?ELFMAG? undeclared (first use in this function)
modprobe.c:491: error: ?SELFMAG? undeclared (first use in this function)
modprobe.c:492: error: ?ELFCLASSNONE? undeclared (first use in this
function)
modprobe.c: In function ?get_section?:
modprobe.c:502: error: ?ELFCLASS32? undeclared (first use in this function)
modprobe.c:504: error: ?ELFCLASS64? undeclared (first use in this function)
modprobe.c: In function ?invalidate_section32?:
modprobe.c:536: error: ?Elf32_Ehdr? undeclared (first use in this function)
modprobe.c:536: error: ?hdr? undeclared (first use in this function)
modprobe.c:537: error: ?Elf32_Shdr? undeclared (first use in this function)
modprobe.c:537: error: ?sechdrs? undeclared (first use in this function)
modprobe.c:543: error: ?SHF_ALLOC? undeclared (first use in this function)
modprobe.c: In function ?invalidate_section64?:
modprobe.c:548: error: ?Elf64_Ehdr? undeclared (first use in this function)
modprobe.c:548: error: ?hdr? undeclared (first use in this function)
modprobe.c:549: error: ?Elf64_Shdr? undeclared (first use in this function)
modprobe.c:549: error: ?sechdrs? undeclared (first use in this function)
modprobe.c:555: error: ?SHF_ALLOC? undeclared (first use in this function)
modprobe.c: In function ?strip_section?:
modprobe.c:564: error: ?ELFCLASS32? undeclared (first use in this function)
modprobe.c:567: error: ?ELFCLASS64? undeclared (first use in this function)
make[1]: *** [modprobe.o] Error 1
make: ***
[/Users/nkinar/Desktop/buildroot-1/buildroot-2009.11/output/toolchain/module-init-tools-3.2.2/depmod]
Error 2
next prev parent reply other threads:[~2009-12-02 22:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 1:39 [Buildroot] Updated status on the compilation of busybox on Mac OS X Nicholas Kinar
2009-11-29 8:46 ` Peter Korsgaard
2009-11-29 14:47 ` Nicholas Kinar
2009-11-29 18:37 ` Peter Korsgaard
2009-11-29 20:31 ` Nicholas Kinar
2009-12-01 13:48 ` Thomas Petazzoni
2009-12-01 15:21 ` Nicholas Kinar
2009-12-01 15:34 ` Peter Korsgaard
2009-12-02 1:47 ` Nicholas Kinar
2009-12-02 15:57 ` Nicholas Kinar
2009-12-02 15:59 ` Austin Foxley
2009-12-02 22:47 ` Nicholas Kinar
2009-12-02 18:40 ` Peter Korsgaard
2009-12-02 22:48 ` Nicholas Kinar
2009-12-02 22:55 ` Nicholas Kinar [this message]
2009-12-03 8:30 ` Peter Korsgaard
2009-12-03 14:54 ` Nicholas Kinar
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=4B16F054.8070104@usask.ca \
--to=n.kinar@usask.ca \
--cc=buildroot@busybox.net \
/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