public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbglaw@lug-owl.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61026] sh-rtems4.11 build of 4.9.0 fails on FreeBSD 10 c++ (clang).
Date: Mon, 05 May 2014 11:08:00 -0000 [thread overview]
Message-ID: <bug-61026-4-zXZ8YcVWel@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61026-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61026
--- Comment #7 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
I'm not 100% sure, but I guess this fix breaks building GCC on
gcc111.fsffrance.org . All build details can be found here:
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=218196
The actual error message is:
g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common
-DHAVE_CONFIG_H -I. -I. -I/home/jbglaw/repos/gcc/gcc
-I/home/jbglaw/repos/gcc/gcc/. -I/home/jbglaw/repos/gcc/gcc/../include
-I/home/jbglaw/repos/gcc/gcc/../libcpp/include -I/opt/cfarm/gmp-latest/include
-I/opt/cfarm/mpfr-latest/include -I/opt/cfarm/mpc-latest/include
-I/home/jbglaw/repos/gcc/gcc/../libdecnumber
-I/home/jbglaw/repos/gcc/gcc/../libdecnumber/dpd -I../libdecnumber
-I/home/jbglaw/repos/gcc/gcc/../libbacktrace -o sh.o -MT sh.o -MMD -MP -MF
./.deps/sh.TPo /home/jbglaw/repos/gcc/gcc/config/sh/sh.c
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:201:41: error: declaration of C function 'off64_t
lseek64(int, off64_t, int)' conflicts with
extern off64_t lseek64(int, off64_t, int);
^
/usr/include/unistd.h:199:14: error: previous declaration 'off_t lseek64(int,
off_t, int)' here
extern off_t lseek(int, off_t, int);
^
In file included from /usr/include/unistd.h:844:0,
from /home/jbglaw/repos/gcc/gcc/system.h:262,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/sys/lockf.h:64:39: error: declaration of C function 'int
lockf64(int, int, off64_t)' conflicts with
extern int lockf64 (int, int, off64_t);
^
/usr/include/sys/lockf.h:62:13: error: previous declaration 'int lockf64(int,
int, off_t)' here
extern int lockf (int, int, off_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:917:38: error: declaration of C function 'int
ftruncate64(int, off64_t)' conflicts with
extern int ftruncate64(int, off64_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:915:14: error: previous declaration 'int ftruncate64(int,
off_t)' here
extern int ftruncate(int, off_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:974:46: error: declaration of C function 'int
truncate64(const char*, off64_t)' conflicts with
extern int truncate64(const char *, off64_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:972:14: error: previous declaration 'int truncate64(const
char*, off_t)' here
extern int truncate(const char *, off_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:262:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/unistd.h:993:54: error: declaration of C function 'ssize_t
pread64(int, void*, size_t, off64_t)' conflicts with
extern ssize_t pread64(int, void *, size_t, off64_t);
^
/usr/include/unistd.h:990:18: error: previous declaration 'ssize_t pread64(int,
void*, size_t, off_t)' here
extern ssize_t pread(int, void *, size_t, off_t);
^
/usr/include/unistd.h:994:61: error: declaration of C function 'ssize_t
pwrite64(int, const void*, size_t, off64_t)' conflicts with
extern ssize_t pwrite64(int, const void *, size_t, off64_t);
^
/usr/include/unistd.h:991:18: error: previous declaration 'ssize_t
pwrite64(int, const void*, size_t, off_t)' here
extern ssize_t pwrite(int, const void *, size_t, off_t);
^
/usr/include/unistd.h:1079:38: error: declaration of C function 'off64_t
fclear64(int, off64_t)' conflicts with
extern off64_t fclear64(int, off64_t);
^
/usr/include/unistd.h:1076:15: error: previous declaration 'off_t fclear64(int,
off_t)' here
extern off_t fclear(int, off_t);
^
/usr/include/unistd.h:1080:53: error: declaration of C function 'int
fsync_range64(int, int, off64_t, off64_t)' conflicts with
extern int fsync_range64(int, int, off64_t, off64_t);
^
/usr/include/unistd.h:1077:13: error: previous declaration 'int
fsync_range64(int, int, off_t, off_t)' here
extern int fsync_range(int, int, off_t, off_t);
^
In file included from /home/jbglaw/repos/gcc/gcc/system.h:389:0,
from /home/jbglaw/repos/gcc/gcc/config/sh/sh.c:27:
/usr/include/sys/mman.h:148:60: error: declaration of C function 'void*
mmap64(void*, size_t, int, int, int, off64_t)' conflicts with
extern void *mmap64(void *, size_t, int, int, int, off64_t);
^
/usr/include/sys/mman.h:143:15: error: previous declaration 'void*
mmap64(void*, size_t, int, int, int, off_t)' here
extern void *mmap(void *, size_t, int, int, int, off_t);
^
make[1]: *** [sh.o] Error 1
However, looking at other recent builds
(http://toolchain.lug-owl.de/buildbot/?limit=10000&target=sh-linux), it seems
that eg. gcc110 happily builds this, so this might be a local installation
issue.
next prev parent reply other threads:[~2014-05-05 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 9:01 [Bug target/61026] New: " chris at contemporary dot net.au
2014-05-01 10:22 ` [Bug target/61026] " redi at gcc dot gnu.org
2014-05-01 21:45 ` joel at gcc dot gnu.org
2014-05-03 7:09 ` olegendo at gcc dot gnu.org
2014-05-03 7:51 ` olegendo at gcc dot gnu.org
2014-05-03 8:18 ` olegendo at gcc dot gnu.org
2014-05-03 8:21 ` olegendo at gcc dot gnu.org
2014-05-03 8:25 ` olegendo at gcc dot gnu.org
2014-05-05 11:08 ` jbglaw@lug-owl.de [this message]
2014-05-05 11:32 ` olegendo at gcc dot gnu.org
2014-05-05 11:47 ` jbglaw@lug-owl.de
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=bug-61026-4-zXZ8YcVWel@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 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).