From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: glibc does not build anymore on i686
Date: Sat, 10 May 2003 11:04:00 -0000 [thread overview]
Message-ID: <u8brybvz9g.fsf@gromit.moeb> (raw)
In file included from ../posix/sched.h:32,
from ../include/sched.h:2,
from ../linuxthreads/sysdeps/pthread/pthread.h:20,
from ../include/pthread.h:1,
from ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:24,
from ../sysdeps/generic/ldsodefs.h:38,
from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
from ../sysdeps/unix/sysv/linux/init-first.c:30:
../sysdeps/unix/sysv/linux/bits/sched.h:96: error: redefinition of `__cpu_mask'
../sysdeps/unix/sysv/linux/bits/sched.h:96: error: `__cpu_mask' previously declared here
../sysdeps/unix/sysv/linux/bits/sched.h:106: error: conflicting types for `cpu_set_t'
../sysdeps/unix/sysv/linux/bits/sched.h:106: error: previous declaration of `cpu_set_t'
make[2]: *** [/builds/glibc/gcc-3.3/csu/init-first.o] Error 1
The problem is that both these files include bits/sched.h:
./posix/sched.h:#include <bits/sched.h>
./linuxthreads/sysdeps/pthread/bits/pthreadtypes.h:#include <bits/sched.h>
and both files are included. But why is pthreadtypes.h including
bits/sched.h? This looks broken since we have:
# error "Never include <bits/sched.h> directly; use <sched.h> instead."
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2003-05-10 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 11:04 Andreas Jaeger [this message]
2003-05-10 17:48 ` Ulrich Drepper
2003-05-11 8:56 ` Andreas Jaeger
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=u8brybvz9g.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/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).