public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: lpesce@uchicago.edu
Cc: David Daney <ddaney@avtrex.com>, gcc help <gcc-help@gcc.gnu.org>
Subject: Re: Issue on X86_64?
Date: Sat, 29 Mar 2008 04:17:00 -0000	[thread overview]
Message-ID: <m38x02tb9p.fsf@google.com> (raw)
In-Reply-To: <20080328222028.BDJ36346@m4500-01.uchicago.edu> (Lorenzo Pesce's message of "Fri\, 28 Mar 2008 22\:20\:28 -0500 \(CDT\)")

Lorenzo Pesce <lpesce@uchicago.edu> writes:

> It seems like they are in "objdir"/x86_64-xxx-gnu/libgfortran.
> Unfortunately, the .o do not seem to be build with as PIC and
> the .lo do not seem to be digestible by g++, gcc. So I don't
> know how to coax them into a dyn lib.

You'll find the PIC versions of the libgfortran object files in the
TARGET/libgfortran/.libs directory.

There are absolutely no guarantees that this will be true in any
future release of gcc.

Ian

  reply	other threads:[~2008-03-29  4:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29  3:21 Lorenzo Pesce
2008-03-29  4:17 ` Ian Lance Taylor [this message]
     [not found] <20080328191557.BDJ30009@m4500-01.uchicago.edu>
2008-03-29  1:02 ` David Daney
  -- strict thread matches above, loose matches on Subject: below --
2008-03-25 21:06 Lorenzo Pesce
2008-03-26 10:03 ` Andrew Haley
2008-03-28 17:20   ` Lorenzo Pesce
2008-03-28 17:45     ` Andrew Haley
2008-03-28 17:57       ` Lorenzo Pesce
2008-03-28 18:07         ` Andrew Haley
2008-03-28 18:41           ` Lorenzo Pesce
2008-03-28 19:55             ` Andrew Haley
2008-03-28 22:31               ` Lorenzo Pesce
2008-03-28 22:51                 ` David Daney

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=m38x02tb9p.fsf@google.com \
    --to=iant@google.com \
    --cc=ddaney@avtrex.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=lpesce@uchicago.edu \
    /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).