Re: Issue on X86_64?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Lorenzo Pesce <lpesce@xxxxxxxxxxxx>
Subject: Re: Issue on X86_64?
From: David Daney <ddaney@xxxxxxxxxx>
Date: Fri, 28 Mar 2008 15:50:35 -0700
Cc: Andrew Haley <aph@xxxxxxxxxx>, gcc-help@xxxxxxxxxxx
In-reply-to: <431E7BBD-FE41-4515-BB9D-A86F3E632931@xxxxxxxxxxxx>
References: <4082B87F-8FC7-42FC-A5CE-EDC6A055621B@xxxxxxxxxxxx> <47EA1F49.7000107@xxxxxxxxxx> <00E58A22-C959-4750-9320-78F023BD5879@xxxxxxxxxxxx> <47ED2EA7.7050406@xxxxxxxxxx> <E92CB149-D1B2-45C5-85C1-16354F5165E2@xxxxxxxxxxxx> <47ED33BC.2000806@xxxxxxxxxx> <D96337C2-86A7-4DAF-B141-AB575499CA21@xxxxxxxxxxxx> <47ED4D1F.10106@xxxxxxxxxx> <431E7BBD-FE41-4515-BB9D-A86F3E632931@xxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.12 (X11/20080226)

Lorenzo Pesce wrote:

However, when I try to build a dynamically linked library to be loadedby java, including the .o files from libgfortran.a

This seems like a bad thing to do. libgfortran.a does not contain PICcode, so its members cannot be put in a shared library. You should linkagainst libgfortran.so


David Daney

References:
- Issue on X86_64?
  - From: Lorenzo Pesce
- Re: Issue on X86_64?
  - From: Andrew Haley
- Re: Issue on X86_64?
  - From: Lorenzo Pesce
- Re: Issue on X86_64?
  - From: Andrew Haley
- Re: Issue on X86_64?
  - From: Lorenzo Pesce
- Re: Issue on X86_64?
  - From: Andrew Haley
- Re: Issue on X86_64?
  - From: Lorenzo Pesce
- Re: Issue on X86_64?
  - From: Andrew Haley
- Re: Issue on X86_64?
  - From: Lorenzo Pesce

Prev by Date: Re: Issue on X86_64?
Next by Date: Re: Signedness of char and puts()
Previous by thread: Re: Issue on X86_64?
Next by thread: Re: Issue on X86_64?
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]