From: Alexey Neyman <stilor@att.net>
To: Titus von Boxberg <titus@elbe-informatik.de>
Cc: crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: canadian build for mingw host: patch for gettext 0.19.8.1
Date: Sat, 22 Apr 2017 04:17:00 -0000 [thread overview]
Message-ID: <d230bf32-d9b9-f842-bff5-8c2c177a71c2@att.net> (raw)
In-Reply-To: <bb9c64d8f77542dcbdeba6e5c6a3b4d0@SOLOWJOW.ELBE.local>
[CC crossgcc list]
Hi Titus,
First off, please send the emails the crossgcc mailing list, not to me
personally - I may not be the only person interested in a certain patch,
etc.
On 04/21/2017 04:12 AM, Titus von Boxberg wrote:
> Hi Alexey,
>
> I had to use the patch below to let ct-ng build gettext 0.19.8.1 for host mingw.
>
> I don't use mingw nor gettext at all (besides for running a cross gcc on windows),
> so I don't really understand why it's required (or rather why mingw defines asprintf).
asprintf is more or less common function now.
Can you describe how you set up the mingw host? I'd like to add it to
our docs and add that to our testing regimen.
As to the patch itself, what was the problem with using asprintf from
mingw's libraries? A build log fragment would be helpful.
> I took the idea for the patch from
> https://lists.freedesktop.org/archives/gstreamer-commits/2015-November/090748.html
>
> Second, it looks strange to me that gettext is built at all for the host.
> gettext is _NEEDED by glibc.
It is needed to enable localization in the toolchain components. I
haven't tested that area much myself, though.
And, I think you got it exactly the other way. gettext is not *needed*
by glibc, it is *a part of glibc*. We only build it for *non-glibc*
hosts/targets.
> For the target: OK, may it be so. But why for the host? glibc shouldn't have
> anything to do with the host? Is that correct?
Hint: not all our supported hosts are glibc-based. If you look at the
build script, you'll notice that gettext is skipped if the host is
*-linux-gnu*.
Regards,
Alexey.
next parent reply other threads:[~2017-04-22 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bb9c64d8f77542dcbdeba6e5c6a3b4d0@SOLOWJOW.ELBE.local>
2017-04-22 4:17 ` Alexey Neyman [this message]
[not found] ` <7ea27c306b3f497ab4c37205eea380a0@SOLOWJOW.ELBE.local>
2017-04-21 18:25 ` AW: " Alexey Neyman
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=d230bf32-d9b9-f842-bff5-8c2c177a71c2@att.net \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
--cc=titus@elbe-informatik.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).