This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: patch for libjava/java/util/Calendar.java

From: Anthony Green <green at redhat dot com>
To: tromey at redhat dot com
Cc: David Daney <ddaney at avtrex dot com>, Mark Wielaard <mark at klomp dot org>, Archit Shah <ashah at redhat dot com>, java-patches at gcc dot gnu dot org
Date: Fri, 11 Nov 2005 05:53:41 -0800
Subject: Re: patch for libjava/java/util/Calendar.java
References: <4373AA9C.3070803@redhat.com> <4373B4E7.1080102@avtrex.com> <1131660857.29262.29.camel@localhost.localdomain> <4373CA2D.7020107@avtrex.com> <m38xvw6p5d.fsf@localhost.localdomain>

On Thu, 2005-11-10 at 16:47 -0700, Tom Tromey wrote:
> * It will, I think, majorly screw users of static linking, as it
>   compiles in resource files.  I think these basically don't work when
>   statically linking, at least not ones compiled into libgcj.a.

Are you just referring to the fact that you have to force the resource
files into the final linked image?

Why don't we, for static linkers, create two .a files: libgcj.a and
libgcj-required.a.  libgcj-required.a would contain all of the .o files
that we need to force into every executable.  

Then we change the .spec file by replacing "-lgcj" with
"-lgcj --whole-archive -lgcj-required --no-whole-archive".

AG

References:
- patch for libjava/java/util/Calendar.java
  - From: Archit Shah
- Re: patch for libjava/java/util/Calendar.java
  - From: David Daney
- Re: patch for libjava/java/util/Calendar.java
  - From: Mark Wielaard
- Re: patch for libjava/java/util/Calendar.java
  - From: David Daney
- Re: patch for libjava/java/util/Calendar.java
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]