public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2873] New: building glibc for 2.6.17+ kernels fails in openat
Date: Mon, 03 Jul 2006 21:12:00 -0000 [thread overview]
Message-ID: <20060703211212.2873.vapier@gentoo.org> (raw)
the openat code uses stdarg functions but the func prototype isnt variable (it
doesnt end in ...) which of course causes a build failure
if current cvs head is configured with:
--enable-kernel=2.6.17
the build bombs:
x86_64-pc-linux-gnu-gcc ../sysdeps/unix/sysv/linux/openat.c -c -std=gnu99 -O2
-Wall -Winline -Wwrite-strings -fmerge-all-constants -g -Wstrict-prototypes
-I../include -I/usr/local/src/gnu/glibc-build/io
-I/usr/local/src/gnu/glibc-build -I../sysdeps/x86_64/elf
-I../nptl/sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86_64
-I../sysdeps/unix/sysv/linux/wordsize-64 -I../nptl/sysdeps/unix/sysv/linux
-I../nptl/sysdeps/pthread -I../sysdeps/pthread
-I../ports/sysdeps/unix/sysv/linux -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu
-I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet
-I../nptl/sysdeps/unix/sysv -I../ports/sysdeps/unix/sysv -I../sysdeps/unix/sysv
-I../sysdeps/unix/x86_64 -I../nptl/sysdeps/unix -I../ports/sysdeps/unix
-I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/fpu
-I../nptl/sysdeps/x86_64 -I../sysdeps/x86_64 -I../sysdeps/wordsize-64
-I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic/elf
-I../sysdeps/generic -I../nptl -I../ports -I.. -I../libio -I. -nostdinc
-isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include -isystem /usr/include
-D_LIBC_REENTRANT -include ../include/libc-symbols.h -o
/usr/local/src/gnu/glibc-build/io/openat.o -MD -MP -MF
/usr/local/src/gnu/glibc-build/io/openat.o.dt -MT
/usr/local/src/gnu/glibc-build/io/openat.o
../sysdeps/unix/sysv/linux/openat.c:74: warning: function declaration isn't a
prototype
../sysdeps/unix/sysv/linux/openat.c:148: warning: function declaration isn't a
prototype
../sysdeps/unix/sysv/linux/openat.c: In function '__OPENAT':
../sysdeps/unix/sysv/linux/openat.c:156: error: 'va_start' used in function with
fixed args
make: *** [/usr/local/src/gnu/glibc-build/io/openat.o] Error 1
--
Summary: building glibc for 2.6.17+ kernels fails in openat
Product: glibc
Version: 2.4
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: vapier at gentoo dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2873
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-07-03 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 21:12 vapier at gentoo dot org [this message]
2006-07-05 12:00 ` [Bug libc/2873] " vapier at gentoo dot org
2006-07-13 12:12 ` thomas at koeller dot dyndns dot org
2006-08-12 20:28 ` drepper at redhat dot com
2006-08-14 11:30 ` mgorohovsky at gmail dot com
2006-08-25 22:47 ` che at chrekh dot se
2006-08-26 5:14 ` vapier at gentoo dot org
2006-08-26 5:14 ` vapier at gentoo dot org
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=20060703211212.2873.vapier@gentoo.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).