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:30:42 +0300 [thread overview]
Message-ID: <50647F32.2010209@petroprogram.com> (raw)
In-Reply-To: <5064763D.8010203@petroprogram.com>
Ok, I finally found it.
Also "BSD obsolete signal functions" (UCLIBC_HAS_OBSOLETE_BSD_SIGNAL) under
"Advanced Library Settings" must be enabled to make this work.
And looking into lipthread/nptl/sem_open.c I revealed that __fxstat64() is
basically equivalent to fstat64() if Largefile support is enabled in uClibc
and otherwise just fstat().
So I can hack that into my application or maybe directly into sys/stat.h
Case solved :)
27.9.2012 18:52, Stefan Fr?berg kirjoitti:
> 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 ?
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2012-09-27 16:30 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
2012-09-27 16:30 ` Stefan Fröberg [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=50647F32.2010209@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