public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/26165]  New: Cannot find libgomp.spec after 'make install' on x86_64 and ppc64
Date: Tue, 07 Feb 2006 21:41:00 -0000	[thread overview]
Message-ID: <bug-26165-91@http.gcc.gnu.org/bugzilla/> (raw)

After 'make install', the installed compiler cannot find libgomp.spec.  The
problem seems to be that we are not looking in <inst>/lib64:

$ export PATH=$HOME/gomp.clean/native.x86_64/bin:$PATH

$ which gcc
~/gomp.clean/native.x86_64/bin/gcc

$ gcc -o a a.c -fopenmp -O2
a.c: In function 'main':
gcc: libgomp.spec: No such file or directory

$ find ~/gomp.clean/native.x86_64 -name libgomp.spec
/home/cygnus/dnovillo/gomp.clean/native.x86_64/lib64/libgomp.spec

$ cp /home/cygnus/dnovillo/gomp.clean/native.x86_64/lib64/libgomp.spec
/home/cygnus/dnovillo/gomp.clean/native.x86_64/lib/libgomp.spec

$ gcc -o a a.c -fopenmp -O2
$ ./a
./a: error while loading shared libraries: libgomp.so.1: cannot open shared
object file: No such file or directory

$ export LD_LIBRARY_PATH=$HOME/gomp.clean/native.x86_64/lib64:$LD_LIBRARY_PATH

$ ./a
I'm thread 0
I'm thread 3
I'm thread 1
I'm thread 2

Perhaps the two problems are related?  This works just fine on x86.  We neither
have to set LD_LIBRARY_PATH by hand nor we need to move libgomp.spec around.


-- 
           Summary: Cannot find libgomp.spec after 'make install' on x86_64
                    and ppc64
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dnovillo at gcc dot gnu dot org
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2006-02-07 21:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 21:41 dnovillo at gcc dot gnu dot org [this message]
2006-03-08 19:05 ` [Bug libgomp/26165] " aldyh at gcc dot gnu dot org
2006-03-08 19:07   ` Andrew Pinski
2006-03-08 19:07 ` pinskia at physics dot uc dot edu
2006-03-09 20:07 ` dnovillo at gcc dot gnu dot org
2006-06-05  9:35 ` martin at mpa-garching dot mpg dot de
2006-06-05  9:55 ` martin at mpa-garching dot mpg dot de
2006-06-08 10:10 ` martin at mpa-garching dot mpg dot de
2006-06-12 21:13 ` dnovillo at gcc dot gnu dot org
2006-06-12 21:18   ` Andrew Pinski
2006-06-12 21:18 ` pinskia at physics dot uc dot edu
2006-10-28 14:27 ` franke dot daniel at gmail dot com
2006-11-23  9:22 ` martin at mpa-garching dot mpg dot de
2007-01-29  9:44 ` doerr at kis dot uni-freiburg dot de
2007-01-29 10:05 ` martin at mpa-garching dot mpg dot de
2007-03-23  7:50 ` martin at mpa-garching dot mpg dot de
2007-10-19  6:34 ` skaller at users dot sourceforge dot net
2008-07-12 16:02 ` gcc at abeckmann dot de
2008-08-12 18:21 ` froydnj at gcc dot gnu dot org
2008-11-12 14:36 ` froydnj at gcc dot gnu dot 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-26165-91@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: 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).