public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/49441] @LDLIBICONV@ lost from installed libgcj.spec
Date: Fri, 17 Jun 2011 00:10:00 -0000	[thread overview]
Message-ID: <bug-49441-8172-F5JtqdPBPz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49441-8172@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jack Howarth <howarth at nitro dot med.uc.edu> 2011-06-17 00:09:42 UTC ---
I don't believe r169822 is the cause but I see what is happening. During the
build two libgcj.spec files are generated. One in
x86_64-apple-darwin11.0.0/libjava, which properly substitutes LDLIBICONV, and a
second in x86_64-apple-darwin11.0.0/i386/libjava which produces an empty string
for LDLIBICONV. A quick examination of the Makefile's in each directory shows
why.

[MacPro:darwin_objdir/x86_64-apple-darwin11.0.0/libjava] root# grep LDLIBICONV
*
Makefile:LDLIBICONV =  -L/sw/lib -liconv 
config.log:LDLIBICONV=' -L/sw/lib -liconv '
config.status:S["LDLIBICONV"]=" -L/sw/lib -liconv "

[[MacPro:x86_64-apple-darwin11.0.0/i386/libjava] root# grep LDLIBICONV *
Makefile:LDLIBICONV =   
config.log:LDLIBICONV='  '
config.status:S["LDLIBICONV"]="  "

It appears that the multi lib build doesn't pass along the value for LDLIBICONV
into the multi lib and that the installed gcj.spec must be coming out of
x86_64-apple-darwin11.0.0/i386/libjava.


  reply	other threads:[~2011-06-17  0:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 14:45 [Bug java/49441] New: " howarth at nitro dot med.uc.edu
2011-06-17  0:10 ` howarth at nitro dot med.uc.edu [this message]
2011-06-17  0:17 ` [Bug java/49441] " howarth at nitro dot med.uc.edu
2011-06-17 12:51 ` howarth at nitro dot med.uc.edu
2011-06-17 13:06 ` dominiq at lps dot ens.fr

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-49441-8172-F5JtqdPBPz@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).