public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/64779] [5 Regression] libffi/src/x86/sysv.S:864: Error: junk at end of line, first unrecognized character is `@' Date: Mon, 26 Jan 2015 17:33:00 -0000 [thread overview] Message-ID: <bug-64779-4-1nOriZHTuR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64779-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64779 Gerald Pfeifer <gerald at pfeifer dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-01-26 Ever confirmed|0 |1 --- Comment #2 from Gerald Pfeifer <gerald at pfeifer dot com> --- I built GCC configured --without-libgcj --without-libffi and the result works just fine on your testcase: % ~/gcc-ref10-i386/bin/gcc -c conftest.s In case this provide some insight, here the same with gcc -v: % ~/gcc-ref10-i386/bin/gcc -v -c conftest.s Using built-in specs. COLLECT_GCC=/home/gerald/gcc-ref10-i386/bin/gcc Target: i386-unknown-freebsd10.1 Configured with: /scratch2/tmp/gerald/gcc-HEAD/configure --prefix=/home/gerald/gcc-ref10-i386 --disable-libgcj --without-libffi --with-gmp=/home/gerald/10-i386 --with-as=/home/gerald/10-i386/bin/as --with-ld=/home/gerald/10-i386/bin/ld Thread model: posix gcc version 5.0.0 20150125 (experimental) (GCC) COLLECT_GCC_OPTIONS='-v' '-c' '-mtune=generic' '-march=i486' /home/gerald/10-i386/bin/as -v -o conftest.o conftest.s GNU assembler version 2.23.2 (i386-portbld-freebsd10.0) using BFD version (GNU Binutils) 2.23.2 COMPILER_PATH=/home/gerald/gcc-ref10-i386/libexec/gcc/i386-unknown-freebsd10.1/5.0.0/:/home/gerald/gcc-ref10-i386/libexec/gcc/i386-unknown-freebsd10.1/5.0.0/:/home/gerald/gcc-ref10-i386/libexec/gcc/i386-unknown-freebsd10.1/:/home/gerald/gcc-ref10-i386/lib/gcc/i386-unknown-freebsd10.1/5.0.0/:/home/gerald/gcc-ref10-i386/lib/gcc/i386-unknown-freebsd10.1/ LIBRARY_PATH=/home/gerald/gcc-ref10-i386/lib/gcc/i386-unknown-freebsd10.1/5.0.0/:/home/gerald/gcc-ref10-i386/lib/gcc/i386-unknown-freebsd10.1/5.0.0/../../../:/lib/:/usr/lib/ COLLECT_GCC_OPTIONS='-v' '-c' '-mtune=generic' '-march=i486' When I build with just --disable-libgcj, the bootstrap also succeeds. It is when I build without this that bootstrap fails in the manner described above.
next prev parent reply other threads:[~2015-01-26 17:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-24 19:00 [Bug libffi/64779] New: " gerald at pfeifer dot com 2015-01-26 11:27 ` [Bug libffi/64779] [5 Regression] " rguenth at gcc dot gnu.org 2015-01-26 14:03 ` jakub at gcc dot gnu.org 2015-01-26 17:33 ` gerald at pfeifer dot com [this message] 2015-01-26 17:56 ` jakub at gcc dot gnu.org 2015-01-26 23:40 ` gerald at pfeifer dot com 2015-01-27 0:29 ` hjl.tools at gmail dot com 2015-01-27 0:49 ` hjl.tools at gmail dot com 2015-01-27 8:21 ` jakub at gcc dot gnu.org 2015-01-27 11:46 ` hjl.tools at gmail dot com 2015-01-27 16:28 ` rth at gcc dot gnu.org 2015-01-27 16:31 ` rth at gcc dot gnu.org 2015-01-27 20:37 ` rth at gcc dot gnu.org 2015-01-28 23:25 ` rth at gcc dot gnu.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=bug-64779-4-1nOriZHTuR@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: linkBe 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).