libg++

libg++

[Daniel Bernstein]

If I want to install libg++ with egcs, do I have to put it in before
compiling egcs, or can it be added afterward?

Thanks..

Re: libg++

[H.J. Lu]

> 
> If I want to install libg++ with egcs, do I have to put it in before
> compiling egcs, or can it be added afterward?
> 

You drop librx and libg++ directories in the tope level egcs source
directory along with gcc. Then you build egcs as usual.

-- 
H.J. Lu (hjl@gnu.org)

Re: libg++

[Manfred Hollstein]

On Tue, 30 June 1998, 09:54:36, bernste@avoda.jct.ac.il wrote:

 > If I want to install libg++ with egcs, do I have to put it in before
 > compiling egcs, or can it be added afterward?
 > 
 > Thanks..
 > 
 > 

If you are talking about the official libg++-2.8.1.1a, it doesn't
matter when you put the stuff into your source tree. Simply rerun
"make all" will correctly configure the new subdirectory and the build 
it.

I guess the same is true with H.J.'s libg++ addons.

manfred

Re: libg++

[Nathan Myers]

Daniel Bernstein wrote:
> 
> If I want to install libg++ with egcs, do I have to put it in before
> compiling egcs, or can it be added afterward?

In case you didn't know... libg++ is considered obsolete
(well, *I* consider it obsolete).  Anyway, it's not being
maintained.

Nathan Myers
ncm@cantrip.org

Re: libg++

[H.J. Lu]

> 
> Daniel Bernstein wrote:
> > 
> > If I want to install libg++ with egcs, do I have to put it in before
> > compiling egcs, or can it be added afterward?
> 
> In case you didn't know... libg++ is considered obsolete
> (well, *I* consider it obsolete).  Anyway, it's not being
> maintained.
> 

But it is a very good test bed for egcs. IMHO, anyone who works
on egcs should get the libg++ addon, just for sanity check.

-- 
H.J. Lu (hjl@gnu.org)

libg++

[Oleg Krivosheev]

Hi,

can someone point out where is 
separate libg++ for egcs?

IMO, it's perfect Q&A for FAQ and
probably we should keep it (i.e. libg++)
in infrastructure dir.

just a thought...

regards

OK

Re: libg++

[H.J. Lu]

> 
> 
> Hi,
> 
> can someone point out where is 
> separate libg++ for egcs?
> 

ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.1-980119.tar.gz


-- 
H.J. Lu (hjl@gnu.org)

libg++

[Lee Iverson]

Is anyone working on reconstructing libg++ so that it will work with
egcs?  I realize that it is somewhat officially considered *obsolete*
but we have a bunch of legacy code that, until we get it converted,
depends critically on libg++.

-------------------------------------------------------------------------------
Lee Iverson     		SRI International
leei@ai.sri.com			333 Ravenswood Ave., Menlo Park CA 94025
http://www.ai.sri.com/~leei/	(650) 859-3307

Re: libg++

[Mumit Khan]

Lee Iverson <leei@ai.sri.com> writes:
> 
> Is anyone working on reconstructing libg++ so that it will work with
> egcs?  I realize that it is somewhat officially considered *obsolete*
> but we have a bunch of legacy code that, until we get it converted,
> depends critically on libg++.
> 

I use a slightly modified version of libg++-2.8.0b6. The only mods are:
    
    - patch from HJ Lu to fix a bug (shows up only with glibc2? Can't
      remember exactly)
    - replace gxx_includedir with gxx_include_dir to conform to the new
      egcs configure (as of egcs-971127 I believe).

Regards,
Mumit -- khan@xraylith.wisc.edu
http://www.xraylith.wisc.edu/~khan/

Re: libg++

[H.J. Lu]

> 
> 
> Is anyone working on reconstructing libg++ so that it will work with
> egcs?  I realize that it is somewhat officially considered *obsolete*
> but we have a bunch of legacy code that, until we get it converted,
> depends critically on libg++.
> 

ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.0b6.3.tar.gz


H.J.

egcs-970828 install

[Weiwen Liu]

Hi,

The program "c++filt" is not installed by "make install" of egcs-970828.

Re: libg++?

[Joe Buck]

> The libg++ directory hasn't been modified because it doesn't relate to the
> standard, and we're not interested in maintaining it anymore (I think;
> right, Ulrich?).  Someone else is welcome to take it over.

The only parts of old libg++ that I think are that interesting anymore are
the random number classes: there's a nice scheme to generate a variety of
types of random numbers with different distributions.  I think these
originally came from Dirk Grunwald's Awesime project, not from Doug Lea.
Ptolemy used them.

Much of the rest of libg++ I would consider obsolete: String, Complex,
the containers, especially now that we have the SGI hashing classes and
singly linked list.  Just the same, some people still use it, so we can
put it out and call it deprecated.

Incorrect i960 linker config

[Stephen Williams]

The LINK_SPEC doesn't deal with the -mjx and -mrp switches. Also,
ld handles not being given an architecture switch well enough by
looking at what its got. This very simply patch fixes the link spec
by adding the new Jx target types.

NOTE: I think I was the one who submitted the -mjx spec entries for the
assembler, so this is my error I'm correcting:-) (Joel, I'm suprised that
you missed this. I would have thought it would effect RTEMS/i960 links:-)

*** dist/egcs-970828/gcc/config/i960/i960.h     Mon Aug 11 08:57:28 1997
--- egcs-970828/gcc/config/i960/i960.h  Fri Aug 29 23:45:01 1997
***************
*** 81,87 ****
  #define LINK_SPEC \
        "%{mka:-AKA}%{mkb:-AKB}%{msa:-ASA}%{msb:-ASB}\
        %{mmc:-AMC}%{mca:-ACA}%{mcc:-ACC}%{mcf:-ACF}\
!       %{!mka:%{!mkb:%{!msa:%{!msb:%{!mmc:%{!mca:%{!mcc:%{!mcf:-AKB}}}}}}}}\
        %{mbout:-Fbout}%{mcoff:-Fcoff}\
        %{mlink-relax:-relax}"
  
--- 81,87 ----
  #define LINK_SPEC \
        "%{mka:-AKA}%{mkb:-AKB}%{msa:-ASA}%{msb:-ASB}\
        %{mmc:-AMC}%{mca:-ACA}%{mcc:-ACC}%{mcf:-ACF}\
!         %{mja:-AJX}%{mjd:-AJX}%{mjf:-AJX}%{mrp:-AJX}\
        %{mbout:-Fbout}%{mcoff:-Fcoff}\
        %{mlink-relax:-relax}"
  

-- 
Steve Williams
steve@icarus.com
steve@picturel.com

"The woods are lovely, dark and deep.  But I have promises to keep,
And lines to code before I sleep, And lines to code before I sleep."

Re: libg++?

[Jason Merrill]

>>>>> Chip Salzenberg  writes:

> Could someone please explain the relationships among libio, libstd++, and
> libg++?  And given all the activity in C++, could someone explain why
> libg++ hasn't been modified since 14 February 1997 (version 2.8.0b6)?

libio is Per's iostream code (and stdio, but most targets don't use that).
libstdc++ is the rest of the standard library.
libg++ is Doug Lea's old C++ class library.

The libg++ directory hasn't been modified because it doesn't relate to the
standard, and we're not interested in maintaining it anymore (I think;
right, Ulrich?).  Someone else is welcome to take it over.

Jason

libg++?

[Chip Salzenberg]

Could someone please explain the relationships among libio, libstd++, and
libg++?  And given all the activity in C++, could someone explain why
libg++ hasn't been modified since 14 February 1997 (version 2.8.0b6)?
-- 
Chip Salzenberg          - a.k.a. -           
 (Roller coaster on camera:)  "Wow, this square quarter mile
    has unbelievably good light rail transit!"  // MST3K