Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Angirasa <agnirasa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of buildroot on Mac OS X
Date: Tue, 18 Nov 2008 07:59:30 -0800	[thread overview]
Message-ID: <4922E662.9010706@gmail.com> (raw)
In-Reply-To: <873ahpb5wv.fsf@macbook.be.48ers.dk>


They are mainly related to the compilation of ulibc gcc and to my best
knowledge are there because of use of glibc.

The Mac OS X libs are not compatible with glibc usage it seems.
Following are the exact errors after I force it to use the Mac OS X
library.


/usr/bin/gcc -c   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H
-DGENERATOR_FILE -I. -Ibuild
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/build
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/../include
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/../libcpp/include
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gmp/include
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/mpfr/include
-I/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/../libdecnumber
-I../libdecnumber    -o build/genmodes.o
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/genmodes.c
In file included from /usr/include/sys/wait.h:117,
                 from /usr/include/stdlib.h:65,
                 from
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/system.h:207,
                 from
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/genmodes.c:22:
/usr/include/sys/resource.h:88: error: two or more data types in
declaration specifiers
In file included from
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/genmodes.c:22:
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/system.h:397:20:
error: malloc.h: No such file or directory
In file included from
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/genmodes.c:22:
/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2/gcc/system.h:417:
error: conflicting types for ?strsignal?
/usr/include/string.h:136: error: previous declaration of ?strsignal?
was here
make[3]: *** [build/genmodes.o] Error 1
make[2]: *** [all-gcc] Error 2
make[1]: *** [all] Error 2
make: ***
[/Users/agnirasa/Documents/Dev/ToolChainS/build/buildroot-avr32-v2.2.1/toolchain_build_avr32/gcc-4.2.2-final/.compiled]
Error 2




Peter Korsgaard wrote:
>>>>>> "Angirasa" == Angirasa  <agnirasa@gmail.com> writes:
> 
>  Angirasa> Hey all,
> 
>  Angirasa> Was just wondering if there is any active
>  Angirasa> work/solution/workaround for having buildroot on Mac OS X.
> 
> We have received patches in the past, but to my knowledge no
> developers are actively using macosx - What problems are you seing
> exactly?
> 

      reply	other threads:[~2008-11-18 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 22:07 [Buildroot] Status of buildroot on Mac OS X Angirasa
2008-11-18 12:00 ` Peter Korsgaard
2008-11-18 15:59   ` Angirasa [this message]

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=4922E662.9010706@gmail.com \
    --to=agnirasa@gmail.com \
    --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