From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: How can I avoid the dreaded "cannot compute suffix of object files"?
Date: Fri, 12 Feb 2010 16:26:00 -0000 [thread overview]
Message-ID: <4B7566DA.3060704@redhat.com> (raw)
In-Reply-To: <4B754B32.8090501@onetel.net>
On 02/12/2010 12:36 PM, Dr. David Kirkby wrote:
>
> OK, I set LD_OPTIONS to
>
> -R/usr/local/gcc-4.4.3/lib -L/usr/local/gcc-4.4.3/lib
>
> GCC 4.4.3 builds fine. There is no more of this "cannot compute suffix
> of object files" rubbish.
>
> However, at runtime, gcc is failing to find gcc_lib.so, so not all
> binaries build.
>
> fatal: libgcc_s.so.1: open failed: No such file or directory
>
> Any ideas Dennis - or anyone else for that matter?
Probably LD_LIBRARY_PATH again? You need to make sure that libgcc_s.so.1
is reachable.
When do you first see this failure?
Andrew.
next prev parent reply other threads:[~2010-02-12 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 14:55 Dennis Clarke
2010-02-11 18:48 ` Dr. David Kirkby
2010-02-11 22:53 ` Dr. David Kirkby
2010-02-12 14:34 ` Dr. David Kirkby
2010-02-12 16:26 ` Andrew Haley [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-11 12:05 Dr. David Kirkby
2010-02-11 13:40 ` Andrew Haley
[not found] ` <4B743F3F.2030805@onetel.net>
[not found] ` <4B744080.2090607@redhat.com>
[not found] ` <4B744459.3050707@onetel.net>
[not found] ` <4B7446A4.6020306@redhat.com>
[not found] ` <4B744DE4.3090504@onetel.net>
[not found] ` <4B7450A1.5060705@redhat.com>
[not found] ` <4B745148.8080401@redhat.com>
2010-02-14 12:07 ` David Kirkby
2010-02-14 12:46 ` Andrew Haley
2010-02-14 16:08 ` Dr. David Kirkby
2010-02-14 20:27 ` Andrew Haley
2010-02-11 17:41 ` Dr. David Kirkby
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=4B7566DA.3060704@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@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).