Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to enable sighold and sigrelse in uClibc ?
Date: Thu, 27 Sep 2012 19:09:23 +0300	[thread overview]
Message-ID: <50647A33.8080500@petroprogram.com> (raw)
In-Reply-To: <CAHXCMMLRnbyOdS+nsTwCiZG1GA7MYh2VL6uEQaiWLeWMV1JyrQ@mail.gmail.com>

Hi Sam

27.9.2012 19:01, Samuel Martin kirjoitti:
> Hi Stefan,
>
> 2012/9/27 Stefan Fr?berg <stefan.froberg@petroprogram.com>:
>> Hello everyone
>>
>> I need to enable sighold() and sigrelse() functions in uClibc (version
>> 0.9.33 using NPTL)
>> and I have enabled the corresponding UCLIBC_SUSV4_LEGACY (Enable SuSv4
>> Legacy or obsolescent functions)
>> option in .config.
>>
>> However, when trying to use those functions in application they are
>> undeclared and
>> indeed, when checking from uClibc source directory libc/signal I see
>> that they are not even compiled
>> (no sighold.o and sigrelse.o).
>>
>> So what else is needed to make sighold.o and sigrelse.o ?
>>
>> Best regards
>> Stefan
>>
>> P.S:
>> Is there __fxstat64() function somewhere in uClibc ?
> Whenever one changes the uclibc configuration, the whole toolchain
> should be rebuilt.
>
> So, after running 'make uclibc-menuconfig', to rebuild everything, you
> should run: 'make clean all'.

Sure, I have done that several times.
But still those two functions are not compiled in.

There *must* be some configuration option that I have missed ....
(scratching head)


>
> Regards,
>

  reply	other threads:[~2012-09-27 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 15:52 [Buildroot] How to enable sighold and sigrelse in uClibc ? Stefan Fröberg
2012-09-27 16:01 ` Samuel Martin
2012-09-27 16:09   ` Stefan Fröberg [this message]
2012-09-27 16:30 ` Stefan Fröberg

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=50647A33.8080500@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --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