public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: gcc@gcc.gnu.org
Subject: Build problem on ia64
Date: Wed, 22 Sep 2004 13:20:00 -0000	[thread overview]
Message-ID: <20040922100014.GA6215@atrey.karlin.mff.cuni.cz> (raw)

Hello,

when configure is run for libstdc++-v3 during build, I get the following error:

configure:2417: checking for C compiler default output file name
configure:2420:  /abuild/gcc-test/gcc/objdir/gcc/xgcc -B/abuild/gcc-test/gcc/objdir/gcc/ -B/usr/local/ia64-unknown-linux-gnu/bin/ -B/usr/local/ia64-unknown-linux-gnu/lib/ -isystem /usr/local/ia64-unknown-linux-gnu/include -isystem /usr/local/ia64-unknown-linux-gnu/sys-include -O2 -g -O2 -O2 -g -O2  conftest.c  >&5
configure:2423: $? = 0
configure:2469: result: a.out
configure:2474: checking whether the C compiler works
configure:2480: ./a.out
./a.out: error while loading shared libraries: libunwind.so.7: cannot open shared object file: No such file or directory
configure:2483: $? = 127
configure:2492: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

libunwind.so.7 is built in gcc directory, but linker apparently is not
told in where to find it (with LD_LIBRARY_PATH set the things work
correctly).

Where is the right place to fix this (I have very little understanding
of how gcc's build system works :-( )?

Zdenek

             reply	other threads:[~2004-09-22 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 13:20 Zdenek Dvorak [this message]
2004-09-22 13:39 ` Paolo Carlini
2004-09-22 16:33 ` H. J. Lu
2004-09-23 20:04   ` Build problem on ia64 (reverting patch on 3.4 branch) Geert Bosch
2004-09-23 20:13     ` H. J. Lu
2004-09-23 21:40       ` Geert Bosch
2004-09-24  0:05         ` H. J. Lu
2004-09-24  0:09           ` H. J. Lu
2004-09-24 20:20             ` Geert Bosch
2004-09-24 20:36               ` H. J. Lu

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=20040922100014.GA6215@atrey.karlin.mff.cuni.cz \
    --to=rakdver@atrey.karlin.mff.cuni.cz \
    --cc=gcc@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).