public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: Oleg Krivosheev <kriol@fnal.gov>
Cc: egcs@cygnus.com
Subject: Re: egcs-980221 problems on Solaris-2.6
Date: Wed, 25 Feb 1998 06:39:00 -0000	[thread overview]
Message-ID: <oryaz0i3aa.fsf@iguacu.dcc.unicamp.br> (raw)
In-Reply-To: <Pine.GSO.3.96.980225000432.2255B-100000@wally>

Oleg Krivosheev writes:

> But the real problem is that all files in pic/
> directory are compiled without -fPIC option - 
> i don't think linker is the cause of the problem...

Mine are...  Did you get the snapshot with CVS, patches or from the
tar file?  There were some problems in the previous snapshot,
regarding PICFLAG and PICFLAG_FOR_TARGET, that may have caused some
confusion in the latest one.  What are PICFLAG and PICFLAG_FOR_TARGET
defined to, in mh-frag and mt-frag?

> ld: Software Generation Utilities - Solaris/ELF (3.0)

that's exactly what I get.

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil

  reply	other threads:[~1998-02-25  6:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-23  2:51 ftp://egcs.cygnus.com/pub/egcs/README Dietmar.Kuehl
1998-02-23  7:41 ` What is at ftp://egcs.cygnus.com/pub/egcs ? Oleg Krivosheev
1998-02-23 15:57   ` Jeffrey A Law
1998-02-23 15:57 ` egcs-980221 problems on Solaris-2.6 Oleg Krivosheev
1998-02-25  6:39   ` Alexandre Oliva
1998-02-25  6:39     ` Oleg Krivosheev
1998-02-25  6:39       ` Alexandre Oliva [this message]
1998-02-24  3:09 ` ftp://egcs.cygnus.com/pub/egcs/README Jeffrey A Law
1998-03-18 17:40 ` ftp://egcs.cygnus.com/pub/egcs/README Oleg Krivosheev

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=oryaz0i3aa.fsf@iguacu.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --cc=egcs@cygnus.com \
    --cc=kriol@fnal.gov \
    /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).