public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/40947] Invalid flag usage: Wl,-rpath, -Wx,-option must appear after -_SYSTYPE_SVR4
Date: Wed, 03 Aug 2011 15:43:00 -0000	[thread overview]
Message-ID: <bug-40947-8172-7ZKcIBIfv3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40947-8172@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-08-03 15:42:46 UTC ---
>> > Invalid flag usage: Wl,-rpath, -Wx,-option must appear after -_SYSTYPE_SVR4 
>
>> What I do see is that if you add some -W option to ld, you get exactly
>> the message you observe.  E.g.
>
> That's stating the obvious... it is essentially what the error message is
> complaining ('flags must be ordered in some way")

Not really: there's no documented -_SYSTYPE_SVR4 flag, and ld doesn't
accept such a flag at all.  The error message is sort of nonsensical.

>> Do you happen to have some environment variable set to -W<something>?
>> Though I have found no hint that ld would check for this, it's a
>> possibility.
>
> No I don't - just tried export |grep W . In any case, 4.6.1 does not show this
> problem, so it seems to be fixed in 4.6.1 somehow; and it is *not*
> full/relative path related.

Still really strange: I've never seen such a ld message before, building
gcc or otherwise.

Anyway, great that it works for you now.

    Rainer


  parent reply	other threads:[~2011-08-03 15:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-40947-8172@http.gcc.gnu.org/bugzilla/>
2010-12-15 14:57 ` htl10 at users dot sourceforge.net
2010-12-15 19:23 ` rwild at gcc dot gnu.org
2010-12-16  0:23 ` htl10 at users dot sourceforge.net
2011-04-30 19:04 ` htl10 at users dot sourceforge.net
2011-04-30 19:16 ` htl10 at users dot sourceforge.net
2011-04-30 20:53 ` htl10 at users dot sourceforge.net
2011-05-01 10:18 ` htl10 at users dot sourceforge.net
2011-07-19 12:10 ` ro at gcc dot gnu.org
2011-07-19 12:12 ` ro at gcc dot gnu.org
2011-08-02 23:32 ` htl10 at users dot sourceforge.net
2011-08-03 11:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-08-03 15:39 ` htl10 at users dot sourceforge.net
2011-08-03 15:43 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-08-05  5:48 ` htl10 at users dot sourceforge.net
2012-09-01 14:32 ` htl10 at users dot sourceforge.net
2012-09-10 16:28 ` htl10 at users dot sourceforge.net
2012-09-10 21:21 ` htl10 at users dot sourceforge.net
2009-08-03  8:55 [Bug libgcj/40947] New: " htl10 at users dot sourceforge dot net
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-8172-7ZKcIBIfv3@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).