public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: libstdc++.a in gcc-lib?
@ 1998-10-09 12:35 Mike Stump
  0 siblings, 0 replies; 8+ messages in thread
From: Mike Stump @ 1998-10-09 12:35 UTC (permalink / raw)
  To: egcs, yumf

> To: egcs@cygnus.com
> Date: Thu, 08 Oct 1998 10:45:08 -0700
> From: Marco Manfai Yu <yumf@ultimatech.com>

>     I am upgrading my compiler from 1.0.3a to 1.1. In the mean time
> I need to compile my code using both compilers from time to time.
> This causes a problem: both compilers have their own libstdc++

Sounds like you forgot to use --prefix, this is the only way it has
ever worked, and will be the only way it ever works in the furture.
People are welcome to prove me wrong.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-09 10:40   ` Marco Manfai Yu
@ 1998-10-09 17:42     ` Jeffrey A Law
  0 siblings, 0 replies; 8+ messages in thread
From: Jeffrey A Law @ 1998-10-09 17:42 UTC (permalink / raw)
  To: Marco Manfai Yu; +Cc: dave madden, egcs

  In message < 199810091708.KAA07984@iago.ultimatech.com.ultimatech.com >you write:
  > 
  > > If you need to run multiple versions of gcc or egcs, the simplest way
  > > to do it is to install them in completely separate trees.  You can
  > > cause this to happen with the "--prefix=/some/special/directory"
  > > argument to configure.  I always install large packages like gcc,
  > > egcs, emacs, gdb, and perl into directories like:
  > > 
  > > 	/usr/local/packages/egcs-1.1b
  > > 
  > 
  > Yes. I am using --prefix now. I am just curious because it seems that
  > gcc's -V mechanism and the gcc-lib/<platform>/<version>/ structure
  > is doing the same thing. If libstdc++.a is in the same place as
  > libgcc.a, I can say
There is an option to put libstdc++ in the same directory as libgcc, but I
wouldn't recommend you use it without seriously considering the consequences.

Like what happens if you build it as a shared library, then delete the
compiler one day...  Poof, any program which used that shared library will
stop working.

jeff

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-08 10:45 Marco Manfai Yu
  1998-10-09  8:42 ` Gerald Pfeifer
  1998-10-09 11:45 ` dave madden
@ 1998-10-09 17:40 ` Alexandre Oliva
  1998-10-09 17:40   ` Marco Manfai Yu
  2 siblings, 1 reply; 8+ messages in thread
From: Alexandre Oliva @ 1998-10-09 17:40 UTC (permalink / raw)
  To: yumf; +Cc: egcs

Marco Manfai Yu <yumf@ultimatech.com> writes:

> The default installation installs libstdc++.a into /usr/local/lib,
> which overwrites the old one. My question is: is it a better idea to
> move libstdc++ into gcc-lib/<version> like libgcc.a?

Try configure --enable-version-specific-runtime-libs

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


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-09 17:40 ` Alexandre Oliva
@ 1998-10-09 17:40   ` Marco Manfai Yu
  0 siblings, 0 replies; 8+ messages in thread
From: Marco Manfai Yu @ 1998-10-09 17:40 UTC (permalink / raw)
  To: Alexandre Oliva; +Cc: yumf, egcs

> 
> Try configure --enable-version-specific-runtime-libs

This is what I'm looking for. I recompiled my egcs 1.1. It works
great.

Thanks,

Marco Yu
yumf@ultimatech.com

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-08 10:45 Marco Manfai Yu
  1998-10-09  8:42 ` Gerald Pfeifer
@ 1998-10-09 11:45 ` dave madden
  1998-10-09 10:40   ` Marco Manfai Yu
  1998-10-09 17:40 ` Alexandre Oliva
  2 siblings, 1 reply; 8+ messages in thread
From: dave madden @ 1998-10-09 11:45 UTC (permalink / raw)
  To: yumf; +Cc: egcs

 =>From: Marco Manfai Yu <yumf@ultimatech.com>
 =>...
 =>    I am upgrading my compiler from 1.0.3a to 1.1. In the mean time
 =>I need to compile my code using both compilers from time to time.
 =>This causes a problem: both compilers have their own libstdc++ and
 =>they are not compatible. The default installation installs libstdc++.a
 =>into /usr/local/lib, which overwrites the old one. My question is:
 =>is it a better idea to move libstdc++ into gcc-lib/<version> like
 =>libgcc.a? Seems to me that the compiler depends on the library to
 =>provide certain functions (such as EH) so libstdc++ is
 =>compiler-specific anyway.
 =>
 =>Comments?

If you need to run multiple versions of gcc or egcs, the simplest way
to do it is to install them in completely separate trees.  You can
cause this to happen with the "--prefix=/some/special/directory"
argument to configure.  I always install large packages like gcc,
egcs, emacs, gdb, and perl into directories like:

	/usr/local/packages/egcs-1.1b

Then I symlink the binaries for the version I want to use by default
into /usr/local/bin:

	ln -s /usr/local/packages/egcs-1.1b/bin/gcc /usr/local/bin/egcs
	ln -s /usr/local/packages/egcs-1.1b/bin/g++ /usr/local/bin/egcs++

This way, the libraries and support files for a specific version live
in a place where no other version will accidentally find them, and I
can remove all the parts of an old version without having to spelunk
through common directories looking for pieces of a package whose names
I don't even know.

d.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-09 11:45 ` dave madden
@ 1998-10-09 10:40   ` Marco Manfai Yu
  1998-10-09 17:42     ` Jeffrey A Law
  0 siblings, 1 reply; 8+ messages in thread
From: Marco Manfai Yu @ 1998-10-09 10:40 UTC (permalink / raw)
  To: dave madden; +Cc: yumf, egcs

> If you need to run multiple versions of gcc or egcs, the simplest way
> to do it is to install them in completely separate trees.  You can
> cause this to happen with the "--prefix=/some/special/directory"
> argument to configure.  I always install large packages like gcc,
> egcs, emacs, gdb, and perl into directories like:
> 
> 	/usr/local/packages/egcs-1.1b
> 

Yes. I am using --prefix now. I am just curious because it seems that
gcc's -V mechanism and the gcc-lib/<platform>/<version>/ structure
is doing the same thing. If libstdc++.a is in the same place as
libgcc.a, I can say

% g++

to run the latest g++ version and

% g++ -Vegcs-2.90.29

to get my 1.0.3a.

Actually I can even install gcc-2.8.1 into the same directory and use
the -V option to run that if I want. I just think that this is a
cleaner way to install multiple versions of the compiler and I (or
other users) can use any of them without changing their paths or
the links to /usr/local/bin.

The compiler works great though. Great job.

Marco Yu
yumf@ultimatech.com

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: libstdc++.a in gcc-lib?
  1998-10-08 10:45 Marco Manfai Yu
@ 1998-10-09  8:42 ` Gerald Pfeifer
  1998-10-09 11:45 ` dave madden
  1998-10-09 17:40 ` Alexandre Oliva
  2 siblings, 0 replies; 8+ messages in thread
From: Gerald Pfeifer @ 1998-10-09  8:42 UTC (permalink / raw)
  To: Marco Manfai Yu; +Cc: egcs

On Thu, 8 Oct 1998, Marco Manfai Yu wrote:
> I need to compile my code using both compilers from time to time.
> This causes a problem: both compilers have their own libstdc++ and
> they are not compatible.

How about using `configure --prefix=/some/path/egcs-version/` ?

Gerald
-- 
Gerald Pfeifer (Jerry)      Vienna University of Technology
pfeifer@dbai.tuwien.ac.at   http://www.dbai.tuwien.ac.at/~pfeifer/


^ permalink raw reply	[flat|nested] 8+ messages in thread

* libstdc++.a in gcc-lib?
@ 1998-10-08 10:45 Marco Manfai Yu
  1998-10-09  8:42 ` Gerald Pfeifer
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Marco Manfai Yu @ 1998-10-08 10:45 UTC (permalink / raw)
  To: egcs

Hi,

    I am upgrading my compiler from 1.0.3a to 1.1. In the mean time
I need to compile my code using both compilers from time to time.
This causes a problem: both compilers have their own libstdc++ and
they are not compatible. The default installation installs libstdc++.a
into /usr/local/lib, which overwrites the old one. My question is:
is it a better idea to move libstdc++ into gcc-lib/<version> like
libgcc.a? Seems to me that the compiler depends on the library to
provide certain functions (such as EH) so libstdc++ is
compiler-specific anyway.

Comments?

Marco Yu
yumf@ultimatech.com

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~1998-10-09 17:42 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-10-09 12:35 libstdc++.a in gcc-lib? Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
1998-10-08 10:45 Marco Manfai Yu
1998-10-09  8:42 ` Gerald Pfeifer
1998-10-09 11:45 ` dave madden
1998-10-09 10:40   ` Marco Manfai Yu
1998-10-09 17:42     ` Jeffrey A Law
1998-10-09 17:40 ` Alexandre Oliva
1998-10-09 17:40   ` Marco Manfai Yu

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).