From: dpace <dpace@echo-on.net>
To: help-gcc@gnu.org
Subject: Re: gcc don't run.
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <38571031.FD89D9EC@echo-on.net> (raw)
Message-ID: <19991231222400._ZDpg5JbrwspEtAONcz7qR0gmcHIsZ1Xjdrp4j9sPVs@z> (raw)
In-Reply-To: <830k0v$ka9$1@news.x-echo.com>
eflorent wrote:
> Hello,
>
> When I type :
> gcc -v
> I get :
> error : bad tag flag in ld.so
> etc...
> instead of gcc v2.3.7 or things like that.
> I suppose it's a very
> I'm trying to compile a Perl Module and Make tell me that I should hunt
> for a compiler.
> I use RedHat 6.0 (installed 2 minutes before) on a PII-350.
>
> Does anyone 've some tips ?
> May I document a little bit more the message ? Actually I push my comput
> er throught the window. I'm on a public terminal. Help ! I can't documen
> t about gcc config. Whe should I look for more "man".
>
> eflorent@starlynx.com
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Article poste via Voila News - http://www.news.voila.fr
> Le : Sun Dec 12 17:54:55 1999 depuis l'IP : 193.250.86.63
Try running ldconfig to update the library links and library cache.
You could also try upgrade the ld.so library in /lib and then
run ldconfig to register it.
But be very careful because you can freeze your system with
some of those /lib libraries.
/sbin/sln can be used to put the old ld.so in place
if your system fails. It is static version of ln that can work
when the dynamic libraries are damaged (be forewarned).
--
David Pace - Free commodity/stock graphing software
and Linux links at http://www.daveware.com
next prev parent reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-12 19:59 eflorent
1999-12-14 19:50 ` dpace [this message]
1999-12-31 22:24 ` dpace
1999-12-31 22:24 ` eflorent
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=38571031.FD89D9EC@echo-on.net \
--to=dpace@echo-on.net \
--cc=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).