From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: sig_atomic_t disappeared from klibc
Date: Thu, 27 Nov 2003 14:19:19 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106994281929616@msgid-missing> (raw)
What should be used for sig_atomic_t in the future?
klibc doesnt define it anymore. Maybe all archs have to define a
sig_atomic_t?
In file included from udevdb.c:39:
tdb/tdb.h:131: parse error before '*' token
tdb/tdb.h:131: warning: function declaration isn't a prototype
make: *** [udevdb.o] Error 1
Bad exit status from /var/tmp/rpm-tmp.80116 (%build)
olaf@mandarine:/usr/src/packages/SOURCES> grep -wr sig_atomic_t ../BUILD/udev-007/
../BUILD/udev-007/klibc/klibc/arch/ia64/include/klibc/archsignal.h:typedef int sig_atomic_t;
../BUILD/udev-007/tdb/tdb.c:static sig_atomic_t *palarm_fired;
../BUILD/udev-007/tdb/tdb.c:void tdb_set_lock_alarm(sig_atomic_t *palarm)
../BUILD/udev-007/tdb/tdb.h:void tdb_set_lock_alarm(sig_atomic_t *palarm);
../BUILD/udev-007/klibc-0.87/klibc/arch/ia64/include/klibc/archsignal.h:typedef int sig_atomic_t;
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2003-11-27 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 14:19 Olaf Hering [this message]
2003-11-27 14:50 ` sig_atomic_t disappeared from klibc Martin Hicks
2003-12-02 0:17 ` Greg KH
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=marc-linux-hotplug-106994281929616@msgid-missing \
--to=olh@suse.de \
--cc=linux-hotplug@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.