From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option
Date: Fri, 18 Jun 2010 23:28:07 +0200 [thread overview]
Message-ID: <4C1BE4E7.4000404@gmx.net> (raw)
In-Reply-To: <87pqzo9gwj.fsf@macbook.be.48ers.dk>
Am 18.06.2010 23:20, schrieb Peter Korsgaard:
>>>>>> "Ossy" == Ossy<ossy1980@gmx.net> writes:
>
> Ossy> Hi,
> Ossy> Maybe it's known, but it is not only SV4_DEPR. I was forced to
> Ossy> activate "OBSOLETE BSD SIGNALS" too. SV4 is not sufficient for a
> Ossy> successful build.
>
> Ossy> xfsprogs/Config.in:
> Ossy> "Note that xfsprogs needs a toolchain with UCLIBC_SV4_DEPRECATED and
> Ossy> UCLIBC_HAS_OBSOLETE_BSD_SIGNAL enabled"
>
> Strange. I did see the comment, but it built here without.
I tried it out myself without OBSOLETE_BSD_SIGNALS (after spotted your
commit). But in fact BSD-Signals are mandatory (at least for me). I'm
using Debian squeeze and the same config as I sent in for rsync and
squashtools.
prev parent reply other threads:[~2010-06-18 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 9:48 [Buildroot] [git commit master 1/1] uClibc: 0.9.31.config: enable UCLIBC_SV4_DEPRECATED option Peter Korsgaard
2010-06-18 21:05 ` Ossy
2010-06-18 21:20 ` Peter Korsgaard
2010-06-18 21:28 ` Ossy [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=4C1BE4E7.4000404@gmx.net \
--to=ossy1980@gmx.net \
--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