This is the mail archive of the java@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: Why use '/proc/self/exe' in prims.cc?

From: Ranjit Mathew <rmathew at hotmail dot com>
To: java at gcc dot gnu dot org
Date: Thu, 07 Nov 2002 19:43:31 +0530
Subject: Re: Why use '/proc/self/exe' in prims.cc?
References: <aqdkai$6gi$1@main.gmane.org> <15818.24337.926831.520022@cuddles.cambridge.redhat.com>

Andrew Haley wrote:

This patch should have fixed it:

2002-06-04  H.J. Lu  (hjl@gnu.org)

	* configure.in (--with-newlib): New option:
	Check ${with_newlib} instead of ${with_cross_host} for newlib.
	(HAVE_PROC_SELF_EXE): Defined to 1 only for cross compiling to
	Linux.
	* configure: Regenerated.

Sorry, I'd checked it only with GCJ 3.2 - seeing it still
in GCJ 3.3 (but not actually building with it) made me think
that it'd still have the same adverse effect.

What is the effect of not getting access to the complete
path to the executable? What is it needed for?

Sincerely Yours,
Ranjit.

--
Ranjit Mathew          Email: rmathew AT hotmail DOT com

Bangalore, INDIA.      Web: http://ranjitmathew.tripod.com/

Follow-Ups:
- Re: Why use '/proc/self/exe' in prims.cc?
  - From: Andrew Haley

References:
- Why use '/proc/self/exe' in prims.cc?
  - From: Ranjit Mathew
- Why use '/proc/self/exe' in prims.cc?
  - From: Andrew Haley

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