public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/40947]  New: Invalid flag usage: Wl,-rpath, -Wx,-option must appear after -_SYSTYPE_SVR4
Date: Mon, 03 Aug 2009 08:55:00 -0000	[thread overview]
Message-ID: <bug-40947-10503@http.gcc.gnu.org/bugzilla/> (raw)

svn r150353 - snapshot a few days ago: This is probably quite obvious and easy
to fix? I couldn't work out the syntax of -_SYSTYPE_SVR4...

-------------------------
make[3]: Entering directory
`/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava'
/usr/local/bin/bash ./libtool --tag=GCJ --mode=link
/home/htl10/tmp-build/g-svn/./gcc/gcj
-B/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava/
-B/home/htl10/tmp-build/g-svn/./gcc/ -B/usr/local/alphaev68-dec-osf5.1a/bin/
-B/usr/local/alphaev68-dec-osf5.1a/lib/ -isystem
/usr/local/alphaev68-dec-osf5.1a/include -isystem
/usr/local/alphaev68-dec-osf5.1a/sys-include   
-L/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava -mieee -g -O2  -o
jv-convert --main=gnu.gcj.convert.Convert -rpath /usr/local/lib -shared-libgcc 
  -L/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava/.libs libgcj.la 
libtool: link: /home/htl10/tmp-build/g-svn/./gcc/gcj
-B/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava/
-B/home/htl10/tmp-build/g-svn/./gcc/ -B/usr/local/alphaev68-dec-osf5.1a/bin/
-B/usr/local/alphaev68-dec-osf5.1a/lib/ -isystem
/usr/local/alphaev68-dec-osf5.1a/include -isystem
/usr/local/alphaev68-dec-osf5.1a/sys-include -mieee -g -O2 -o .libs/jv-convert
--main=gnu.gcj.convert.Convert -shared-libgcc 
-L/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava/.libs
-L/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava ./.libs/libgcj.so
-lpthread -lrt -Wl,-rpath -Wl,/usr/local/lib
/bin/ld:
Invalid flag usage: Wl,-rpath, -Wx,-option must appear after -_SYSTYPE_SVR4 
/bin/ld: Usage: /bin/ld [options] file [...]
collect2: ld returned 1 exit status
make[3]: *** [jv-convert] Error 1
make[3]: Leaving directory
`/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/htl10/tmp-build/g-svn/alphaev68-dec-osf5.1a/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/home/htl10/tmp-build/g-svn'
make: *** [all] Error 2
-------------------------


-- 
           Summary: Invalid flag usage: Wl,-rpath, -Wx,-option must appear
                    after -_SYSTYPE_SVR4
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: htl10 at users dot sourceforge dot net
  GCC host triplet: alphaev68-dec-osf5.1a


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40947


             reply	other threads:[~2009-08-03  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03  8:55 htl10 at users dot sourceforge dot net [this message]
2009-08-03  8:57 ` [Bug libgcj/40947] " htl10 at users dot sourceforge dot net
2010-07-14 10:05 ` htl10 at users dot sourceforge dot net
2010-07-15 21:29 ` htl10 at users dot sourceforge dot net

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-40947-10503@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).