From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Updated status on the compilation of busybox on Mac OS X
Date: Sun, 29 Nov 2009 19:37:55 +0100 [thread overview]
Message-ID: <87einh2n3w.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4B128965.2090303@usask.ca> (Nicholas Kinar's message of "Sun\, 29 Nov 2009 08\:47\:01 -0600")
>>>>> "Nicholas" == Nicholas Kinar <n.kinar@usask.ca> writes:
Hi,
Nicholas> Thank you so much for your response! I agree that Linux
Nicholas> systems are much, much better than generic Unix, and I
Nicholas> actually run buildroot for the AVR32 architecture on a very
Nicholas> nice Ubuntu box. (No virtualization required.) However,
Nicholas> there are a few programs that I would also like to use on Mac
Nicholas> OS X, and imho it would be nice to do everything on the same
Nicholas> operating system. I also have some hardware which is
Nicholas> unfortunately not supported on Linux.
OK. I still think you'll have an easier time doing your buildroot work
on a (virtual) Linux box, but it's your choice..
Nicholas> I have tried to compile buildroot on Mac OS X. Using some
Nicholas> packages from the Fink project (i.e. binutils), I can coax
Nicholas> buildroot to partially compile. However, the compilation
Nicholas> seems to crash when it encounters uclibc.
Nicholas> I know that the Gumstix folks seem to keep a separate build
Nicholas> for Mac OS X:
Nicholas> http://docwiki.gumstix.org/index.php/Buildroot_on_MacOSX
Yes, the gumstix people unfortunately haven't been that good at
submitting their fixes back to us :/
Nicholas> To me, it seemed a bit of a shame to keep a separate build,
Nicholas> and it would be nice to perhaps merge this into the main
Nicholas> distribution, at least imho to allow for buildroot to compile
Nicholas> on all Linux and Unix systems. I suppose that my desire to
Nicholas> do compilation on a Unix system is more for philosophical
Nicholas> rather than for practical reasons.
I agree that there isn't any technical reason why BR shouldn't work on
MacOSX, but currently there's no active developers using it (I do write
this on a macbook, but I very rarely boot into macosx).
The problem isn't just getting the makefiles of BR to work on MacOSX,
the biggest problem is all the build scripts of the individual packages.
With that said, patches to make stuff work better on MacOSX are welcome,
as long as they aren't too ugly / add too much extra complexity for such
a rarely used setup.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-11-29 18:37 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 [this message]
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
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=87einh2n3w.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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