From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] localedef: Build fixes for Darwin
Date: Sun, 8 Apr 2012 10:10:47 +0200 [thread overview]
Message-ID: <20120408081047.GF13585@pengutronix.de> (raw)
In-Reply-To: <20120407183017.GA32754@regiomontanus.bwalle.de>
Hi,
On Sat, Apr 07, 2012 at 08:30:17PM +0200, Bernhard Walle wrote:
> * Michael Olbrich <m.olbrich@pengutronix.de> [2012-03-24 13:15]:
> > On Sun, Feb 12, 2012 at 04:44:52PM +0100, Bernhard Walle wrote:
> > > This patch series against the ptx branch in mol/localedef.git makes
> > > localedef compiling on Darwin. Tested on Mac OS 10.7 (Lion).
> > >
> > > I know you suggested using host-gettext-dummy, but that didn't work out of the
> > > box. Creating the host-gettext-dummy rules was easy and it worked, but the
> > > files copied from eglibc didn't compile; fixing that would be much more work
> > > than just defining two macros, so I took the easy way.
> >
> > I finally managed to work on this again. I've merged the patches, created a
> > release and pushed an update to ptxdist. Please test.
>
> Sorry for my late feedback on this. The good news is that host-localedef
> builds with FSF GCC 4.2 [1] (and that was the compiler that I tested
> on my old MacBook when I created the patches).
great.
> 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.
Btw, what's the overall status with ptxdist on MacOS?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-04-08 8:10 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 ` Michael Olbrich [this message]
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 ` [ptxdist] localedef: Build fixes for Darwin Bernhard Walle
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=20120408081047.GF13585@pengutronix.de \
--to=m.olbrich@pengutronix.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