From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] localedef: Build fixes for Darwin
Date: Sun, 8 Apr 2012 16:42:07 +0200 [thread overview]
Message-ID: <20120408144207.GA13618@regiomontanus.bwalle.de> (raw)
In-Reply-To: <20120408081047.GF13585@pengutronix.de>
Hi,
* Michael Olbrich <m.olbrich@pengutronix.de> [2012-04-08 10:10]:
>
> > For LLVM GCC [2] which is used in new XCode versions (the old gcc can
> > still be installed as gcc-apple-4.2 with MacPorts), a small fix is
> > needed, I'll send a patch afterwards.
> >
> > So if you could apply that patch and queue it for future releases that
> > would be awesome. I guess that this issue has nothing to do with MacOS
> > but that LLVM GCC on Linux yields to the same results. However, I also
> > guess that nobody out there uses LLVM GCC on Linux to build such
> > tools...
>
> I've applied the patch. I suppose, for this one patch I wouldn't mind
> having it in ptxdist as well. I'll just drop it when I create the next
> localedef package. So if you create a patch I'll apply it.
Fine, see the next mail.
> Btw, what's the overall status with ptxdist on MacOS?
Quite good. I don't build with all packages enabled, but my Beagleboard
SDK [1] builds without problems. The same for my weather station [2]
which uses Dockstar hardware (Marvell Kirkwood) and a NSLU2 (Intel IXP)
as the second one.
The only exception is the creation of an ubifs image, i.e.
host-mtd-utils. I have something working in [3] but I want to push that
mainline first. If they don't accept it, I can put a large number of
required headers in my elf-h-compat (which I would rename in that case)
so that the changes in mtd-utils are minimal.
Kernel 3.4 should build without any additional patches as Andreas'
changes [4] got accepted and my printf/echo fix [5] now also is
included.
I hope I have some time in the next weeks to provide a small Howto for
ptxdist on Mac OS. Thanks for accepting all the patches and the feedback
on them, BTW.
Regards,
Bernhard
[1] https://bitbucket.org/bwalle/ptxdist-arm-boards
[2] https://bitbucket.org/bwalle/ptxdist-vetero
[3] https://bitbucket.org/bwalle/mtd-utils
[4] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dd2a3acaecd7abb2d43b09a823cf2e4c967fa2ac
[5] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=875de98623fa2b29f0cb19915fe3292ab6daa1cb
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-04-08 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 15:44 Bernhard Walle
2012-02-12 15:56 ` [ptxdist] [PATCH 1/3] Darwin: Define __nonnull when it's not defined Bernhard Walle
2012-02-12 15:56 ` [ptxdist] [PATCH 2/3] Re-generate configure Bernhard Walle
2012-02-12 15:56 ` [ptxdist] [PATCH 3/3] Fix build without gettext Bernhard Walle
2012-03-24 12:15 ` [ptxdist] localedef: Build fixes for Darwin Michael Olbrich
2012-04-07 18:30 ` Bernhard Walle
2012-04-07 18:32 ` [ptxdist] [PATCH] argp-fmtstream.h: Force inlining of 'extern inline' functions Bernhard Walle
2012-04-08 8:10 ` [ptxdist] localedef: Build fixes for Darwin Michael Olbrich
2012-04-08 14:32 ` [ptxdist] [PATCH] host-localedef: Fix build with LLVM GCC Bernhard Walle
2012-04-17 9:17 ` Michael Olbrich
2012-04-08 14:42 ` Bernhard Walle [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=20120408144207.GA13618@regiomontanus.bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/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