Re: egcs and gcc

1999-03-03 Thread Doug Rabson
On Tue, 2 Mar 1999, Chuck Robey wrote: > On Tue, 2 Mar 1999, Doug Rabson wrote: > > > That was put in extremely recently. The reason it doesn't build a shared > > library by default is to avoid potential conflict with the system > > libstdc++. > > > > If you enable it, the port will install the

Re: egcs and gcc

1999-03-02 Thread Chuck Robey
On Tue, 2 Mar 1999, Doug Rabson wrote: > That was put in extremely recently. The reason it doesn't build a shared > library by default is to avoid potential conflict with the system > libstdc++. > > If you enable it, the port will install the shared lib in > /usr/lib/gcc-lib/.../libstdc++.so. Y

gcj (was Re: egcs and gcc)

1999-03-02 Thread Nate Williams
> I'm learning here, don't get upset if I'm all wet. Another thing I note > is that, unlike all the rest of the snapshots of egcs, the pre-release > version (and seemingly only the prerelease version) that the port uses > has gcj, the java tool, cut out. That seems kind of a shame, doesn't > it?

Re: egcs and gcc

1999-03-02 Thread Doug Rabson
On Mon, 1 Mar 1999, Chuck Robey wrote: > On Mon, 1 Mar 1999, Thomas Dean wrote: > > > As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > > should. > > > > How does this get fixed? > > I just noticed that the egcs Makefile has a buried: > > .if defined(WANT_SHAREDLIBS) > CONFI

Re: egcs and gcc

1999-03-01 Thread David O'Brien
> I'm learning here, don't get upset if I'm all wet. Another thing I note > is that, unlike all the rest of the snapshots of egcs, the pre-release > version (and seemingly only the prerelease version) that the port uses > has gcj, the java tool, cut out. egcs-1.{0,1}.x never had the java bits. F

Re: egcs and gcc

1999-03-01 Thread Chuck Robey
On Mon, 1 Mar 1999, Brian Feldman wrote: > You're not concerned about the freezeup? The freezeup had nothign whatsoever to do with the subject at hand. I'm concerned, but this is the *wrong* time to raise it. I am not running a new kernel, not doing any egcs testing at all yet, still in tool-bu

Re: egcs and gcc

1999-03-01 Thread Brian Feldman
On Mon, 1 Mar 1999, Chuck Robey wrote: > On Mon, 1 Mar 1999, David O'Brien wrote: > > > > .if defined(WANT_SHAREDLIBS) > > > CONFIGURE_ARGS+= --enable-shared > > > .endif > > > > > > in it. That's not particularly friendly, I wonder why it was put in > > > there, unless the feature is somehow b

Re: egcs and gcc

1999-03-01 Thread David O'Brien
On Mon, Mar 01, 1999 at 10:10:34PM -0500, Chuck Robey wrote: > I tried taking the gcj part out of the latest egcs snap, and dropping it > inplace in the prerelease version. Grab ftp://ftp.nuxi.com/pub/FreeBSD/egcs-devel-port-990228.tar.gz if you want a portball for the latest snapshot of EGCS.

Re: egcs and gcc

1999-03-01 Thread Chuck Robey
On Mon, 1 Mar 1999, David O'Brien wrote: > > .if defined(WANT_SHAREDLIBS) > > CONFIGURE_ARGS+= --enable-shared > > .endif > > > > in it. That's not particularly friendly, I wonder why it was put in > > there, unless the feature is somehow broken? I'm trying to rebuild it > > now to see what it

Re: egcs and gcc

1999-03-01 Thread Thomas Dean
... > eg++ is totally incompatable with g++ 2.7.x. ... > -- David(obr...@nuxi.com -or- obr...@freebsd.org) Aha! Thanks, tomdean To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: egcs and gcc

1999-03-01 Thread David O'Brien
> As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > should. NO it should NOT! libstdc++.so.2 is matched to g++ 2.7.2.x, NOT egcs. This point is why I won't make the EGCS port have a shared libstdc++ by default. What happens when you move an eg++ produced binary to a machine w/

Re: egcs and gcc

1999-03-01 Thread David O'Brien
> .if defined(WANT_SHAREDLIBS) > CONFIGURE_ARGS+= --enable-shared > .endif > > in it. That's not particularly friendly, I wonder why it was put in > there, unless the feature is somehow broken? I'm trying to rebuild it > now to see what it then installs. Because people like a previous poster th

Re: egcs and gcc

1999-03-01 Thread Thomas Dean
# pwd; ls /usr/local/lib/gcc-lib/i386-unknown-freebsd4.0/egcs-2.91.60 SYSCALLS.c.Xcollect2* crtend.olibg2c.alibstdc++.a cc1*cpp*crtendS.o libgcc.aspecs cc1obj* crtbegin.o f771* libiberty.a cc1plus*crtbegi

Re: egcs and gcc

1999-03-01 Thread Chuck Robey
On Mon, 1 Mar 1999, Thomas Dean wrote: > As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it > should. > > How does this get fixed? I just noticed that the egcs Makefile has a buried: .if defined(WANT_SHAREDLIBS) CONFIGURE_ARGS+= --enable-shared .endif in it. That's not particu

Re: egcs and gcc

1999-03-01 Thread Thomas Dean
As suspected, eg++ is using libstdc++.a, not libstdc++.so.2, as it should. How does this get fixed? tomdean == # g++ -m486 -O2 hello.cc -o hello # ldd hello hello: libg++.so.4 => /usr/lib/libg++.so.4 (0x28051000) libstdc++.so.2 => /usr

Re: egcs and gcc

1999-03-01 Thread Mark Murray
Thomas Dean wrote: > # file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), \ >dynamically linked, stripped > # time hello > Hello, world. > 0.02 real 0.00 user 0.02 sys Please add to that list the output of "ldd " for each executable. M