Re: gcc and /usr/lib/libstdc++.so.3

2000-02-12 Thread David O'Brien

On Thu, Feb 10, 2000 at 08:34:28PM -0500, Donn Miller wrote:
 Nope.  When I ran buildword, I used CFLAGS='-mpentium -O3 -pipe'.  I

We don't support building world with -O3.  Before continuing this path,
please try the *stock* values.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-12 Thread David O'Brien

On Thu, Feb 10, 2000 at 08:24:09AM -0500, Donn Miller wrote:
 I know that the standard gcc-2.95.2 itself has libstdc++ built in, so
 there's no separate library there.

Huh???  Try this:

cd /usr/local/lib/gcc-lib
find . -name libstdc++.a


Don't confuse shared libs vs. static ones; with a total lack.

 What advantage do we gain by having libstdc++ separated out?

We don't.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-10 Thread Will Andrews

On Wed, Feb 09, 2000 at 11:53:47AM -0500, Donn Miller wrote:
 /usr/lib/libstdc++.so.3: undefined reference to `exception type_info node'
 /usr/lib/libstdc++.so.3: undefined reference to `exception virtual table'
 /usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new'

Just a thought - have you tried -fno-c++--exceptions (or similar) ?
I'm not sure if that would fix it, though.

-- 
Will Andrews [EMAIL PROTECTED]
GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ 
G+ e- h! r--+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-10 Thread Donn Miller

Will Andrews wrote:
 
 On Wed, Feb 09, 2000 at 11:53:47AM -0500, Donn Miller wrote:
  /usr/lib/libstdc++.so.3: undefined reference to `exception type_info node'
  /usr/lib/libstdc++.so.3: undefined reference to `exception virtual table'
  /usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new'
 
 Just a thought - have you tried -fno-c++--exceptions (or similar) ?
 I'm not sure if that would fix it, though.

I think maybe you mean -fno-vtable-thunks?  Also, why do we have a
separate libstdc++?  I know that the standard gcc-2.95.2 itself has
libstdc++ built in, so there's no separate library there.  What
advantage do we gain by having libstdc++ separated out?  Not a
criticism - just wondering.

- Donn


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-10 Thread German Tischler

On Tue, Feb 08, 2000 at 06:35:58PM +0100, Maxim Sobolev wrote:
 Donn Miller wrote:
 
  I am running the lastest -current (just did a cvsup followed by a make
  world last night).  I am getting these link errors when trying to compile
  the developement version of kdesupport, which I obtained thru cvsup.  (KDE
  uses cvsup for its development versions.)
 
  I get the following errors.  I have also installed the latest development
  snapshot of gcc 2.96 into /usr/local/bin, and I don't get these errors.
 
  gmake[5]: Entering directory
  `/usr/home/dmmiller/compile/kde/kdesupport/odbc/uni
  xODBC/odbcinst/cmd'
  /bin/sh ../../../../libtool --silent --mode=link gcc  -mpentium -O3 -pipe

Ok, I just tried this. This is a config error in KDE-current.
If you use ,g++' instead of ,gcc` in the above line, it will compile.

  -s -o
  odbcinst  odbcinst.o ../libodbcinst.la ../../lst/libuodbclst.la
  /usr/lib/libstdc++.so.3: undefined reference to `exception type_info
  function'
  [...]
  gmake[5]: *** [odbcinst] Error 1
 
 Absolutely the same is here on just builded/installed -current. Interesting
 that two days ago I had compiled kdesupport w/o this problem on the -current
 system compiled on February 3. Therefore bug in question was introduced during
 Feb 3 - Feb 8 period.

See above. This is not a problem of FreeBSD. Using a C compiler for linking
C++ just does not work.

-- 
German Tischler, [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-09 Thread Maxim Sobolev

John Polstra wrote:

 In article [EMAIL PROTECTED],
 Maxim Sobolev  [EMAIL PROTECTED] wrote:
  Donn Miller wrote:
 
   I am running the lastest -current (just did a cvsup followed by a make
   world last night).  I am getting these link errors when trying to compile
   the developement version of kdesupport, which I obtained thru cvsup.  (KDE
   uses cvsup for its development versions.)
  
   I get the following errors.  I have also installed the latest development
   snapshot of gcc 2.96 into /usr/local/bin, and I don't get these errors.
  
   gmake[5]: Entering directory
   `/usr/home/dmmiller/compile/kde/kdesupport/odbc/uni
   xODBC/odbcinst/cmd'
   /bin/sh ../../../../libtool --silent --mode=link gcc  -mpentium -O3 -pipe
   -s -o
   odbcinst  odbcinst.o ../libodbcinst.la ../../lst/libuodbclst.la
   /usr/lib/libstdc++.so.3: undefined reference to `exception type_info
   function'
   [...]
   gmake[5]: *** [odbcinst] Error 1
 
  Absolutely the same is here on just builded/installed -current. Interesting
  that two days ago I had compiled kdesupport w/o this problem on the -current
  system compiled on February 3. Therefore bug in question was introduced during
  Feb 3 - Feb 8 period.

 Are you sure you're not just hitting this problem described in
 src/UPDATING?

 2124:
 The default way that virtual tables in our default C++

No, because since 2124 I've recompiled both world (several times actually) and all
C++ libs used by the kde. If you will read my previous message thoughtfully, you will
notice that after Jan 24 I had successfully compiled kdesupport on system
builded/installed on Feb 3.

-Maxim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-09 Thread John Polstra

In article [EMAIL PROTECTED],
Maxim Sobolev  [EMAIL PROTECTED] wrote:
 John Polstra wrote:
 
  Are you sure you're not just hitting this problem described in
  src/UPDATING?
 
  2124:
  The default way that virtual tables in our default C++
 
 No, because since 2124 I've recompiled both world (several times
 actually) and all C++ libs used by the kde. If you will read my
 previous message thoughtfully, you will notice that after Jan 24 I
 had successfully compiled kdesupport on system builded/installed on
 Feb 3.

Sheesh, chill out.  I'm just trying to help you.  I did read your
message "thoughtfully."  That's why I wrote, "Are you sure ...?"
rather than, "Hey dumbo, read UPDATING!"  I thought (and still think)
you might possibly have missed rebuilding one of the libraries.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-09 Thread Donn Miller

On Wed, 9 Feb 2000, John Polstra wrote:

 In article [EMAIL PROTECTED],
 Maxim Sobolev  [EMAIL PROTECTED] wrote:

  No, because since 2124 I've recompiled both world (several times
  actually) and all C++ libs used by the kde. If you will read my
  previous message thoughtfully, you will notice that after Jan 24 I
  had successfully compiled kdesupport on system builded/installed on
  Feb 3.

That's my experience also.  I just rebuilt the world on Feb  8, and I
rebuilt Qt, which KDE uses, last night.  No dice.  I still get errors like

/usr/lib/libstdc++.so.3: undefined reference to `exception type_info node'
/usr/lib/libstdc++.so.3: undefined reference to `exception virtual table'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new'

 Sheesh, chill out.  I'm just trying to help you.  I did read your
 message "thoughtfully."  That's why I wrote, "Are you sure ...?"
 rather than, "Hey dumbo, read UPDATING!"  I thought (and still think)
 you might possibly have missed rebuilding one of the libraries.

I rebuilt what I thought were the libs I needed, which would be Qt.  I
don't know if kdesupport is linking with Qt at all, but just in case, I
rebuilt Qt with the new world.  Still, the errors persist.  I think the
next step might be to notify the KDE developers via the comp.windows.x.kde
NG.  Is this bug specific to FreeBSD, or is it a bug of gcc 2.95.2 in
general?

Anyways, I installed gcc version 2.96 2131, which is a snapshot.  I
was able to compile kdesupport with no such errors.  However,
compiling kdelibs is what gives me the libstdc++ errors, because Qt is
linked to gcc 2.95.2.  I tried to compile Qt with gcc 2.96
2131.  However, as I soon found out, the development version has a
ghastly memory leak, which soon ate up all my memory and swap
(64M+130M).  So, I was unable to recompile Qt with 2.96 to complete the
compilation.

- Donn



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-09 Thread Maxim Sobolev

John Polstra wrote:

 In article [EMAIL PROTECTED],
 Maxim Sobolev  [EMAIL PROTECTED] wrote:
  John Polstra wrote:
 
   Are you sure you're not just hitting this problem described in
   src/UPDATING?
  
   2124:
   The default way that virtual tables in our default C++
 
  No, because since 2124 I've recompiled both world (several times
  actually) and all C++ libs used by the kde. If you will read my
  previous message thoughtfully, you will notice that after Jan 24 I
  had successfully compiled kdesupport on system builded/installed on
  Feb 3.

 Sheesh, chill out.  I'm just trying to help you.  I did read your
 message "thoughtfully."  That's why I wrote, "Are you sure ...?"
 rather than, "Hey dumbo, read UPDATING!"  I thought (and still think)
 you might possibly have missed rebuilding one of the libraries.

OK, I've checked once more - all c++ libs I have in my
/usr/lib:/usr/X11R6/lib:/usr/local/lib directories have been recompiled after
c++ changes. Furthermore, when I'm forced this odbcinst to be linked against
static libstdc++.a (by moving libstdc++.so* outside of /usr/lib) all problems
dissapeared, so it could not be mixed libraries or problems in kdesupport
itself.

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



gcc and /usr/lib/libstdc++.so.3

2000-02-08 Thread Donn Miller

I am running the lastest -current (just did a cvsup followed by a make
world last night).  I am getting these link errors when trying to compile
the developement version of kdesupport, which I obtained thru cvsup.  (KDE
uses cvsup for its development versions.)

I get the following errors.  I have also installed the latest development
snapshot of gcc 2.96 into /usr/local/bin, and I don't get these errors.

gmake[5]: Entering directory
`/usr/home/dmmiller/compile/kde/kdesupport/odbc/uni
xODBC/odbcinst/cmd'
/bin/sh ../../../../libtool --silent --mode=link gcc  -mpentium -O3 -pipe
-s -o
odbcinst  odbcinst.o ../libodbcinst.la ../../lst/libuodbclst.la
/usr/lib/libstdc++.so.3: undefined reference to `exception type_info
function'
/usr/lib/libstdc++.so.3: undefined reference to `__cp_push_exception'
/usr/lib/libstdc++.so.3: undefined reference to `__rtti_user'
/usr/lib/libstdc++.so.3: undefined reference to `__rtti_si'
/usr/lib/libstdc++.so.3: undefined reference to `__get_eh_context'
/usr/lib/libstdc++.so.3: undefined reference to `__sjthrow'
/usr/lib/libstdc++.so.3: undefined reference to `terminate(void)'
/usr/lib/libstdc++.so.3: undefined reference to `exception type_info node'
/usr/lib/libstdc++.so.3: undefined reference to `exception virtual table'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_delete'
/usr/lib/libstdc++.so.3: undefined reference to `__rtti_class'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_delete'
/usr/lib/libstdc++.so.3: undefined reference to `__terminate'
/usr/lib/libstdc++.so.3: undefined reference to `__builtin_new'
/usr/lib/libstdc++.so.3: undefined reference to `__eh_alloc'
gmake[5]: *** [odbcinst] Error 1

I'd just like to let you guys know in case this is a problem with our
stock gcc in current.  Like I said, it compiled fine with my compiler in
/usr/local:

$ /usr/local/bin/gcc -v
Reading specs from 
/usr/local/lib/gcc-lib/i386-unknown-freebsdelf4.0/2.96/specs
gcc version 2.96 2131 (experimental)

But, the stock gcc (2.95.2) is the one that gives me these errors.

 - Donn



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: gcc and /usr/lib/libstdc++.so.3

2000-02-08 Thread Maxim Sobolev

Donn Miller wrote:

 I am running the lastest -current (just did a cvsup followed by a make
 world last night).  I am getting these link errors when trying to compile
 the developement version of kdesupport, which I obtained thru cvsup.  (KDE
 uses cvsup for its development versions.)

 I get the following errors.  I have also installed the latest development
 snapshot of gcc 2.96 into /usr/local/bin, and I don't get these errors.

 gmake[5]: Entering directory
 `/usr/home/dmmiller/compile/kde/kdesupport/odbc/uni
 xODBC/odbcinst/cmd'
 /bin/sh ../../../../libtool --silent --mode=link gcc  -mpentium -O3 -pipe
 -s -o
 odbcinst  odbcinst.o ../libodbcinst.la ../../lst/libuodbclst.la
 /usr/lib/libstdc++.so.3: undefined reference to `exception type_info
 function'
 [...]
 gmake[5]: *** [odbcinst] Error 1

Absolutely the same is here on just builded/installed -current. Interesting
that two days ago I had compiled kdesupport w/o this problem on the -current
system compiled on February 3. Therefore bug in question was introduced during
Feb 3 - Feb 8 period.

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



libstdc++.so.3

2000-01-30 Thread Edwin Culp

I make a new world today after reinstalling xinstall and thought that
along with recompiling my applications that are having problems that I
assume started with the c++ compiler change, but I have recompiled
several applications and still have the errors.

If someone would tell me what I am doing wrong.  This is from the latest
version of mysql that I just compiled.

Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
symbol
"_vt$9exception"

TIA,

ed




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: libstdc++.so.3

2000-01-30 Thread Chris D. Faulhaber

On Sun, 30 Jan 2000, Edwin Culp wrote:

 I make a new world today after reinstalling xinstall and thought that
 along with recompiling my applications that are having problems that I
 assume started with the c++ compiler change, but I have recompiled
 several applications and still have the errors.
 
 If someone would tell me what I am doing wrong.  This is from the latest
 version of mysql that I just compiled.
 
 Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
 symbol
 "_vt$9exception"
 

Please read the first 2124 entry of src/UPDATING.

-
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: libstdc++.so.3

2000-01-30 Thread Edwin Culp

Looks like I have to cvsup again, it's not in my UPDATING from 11:40 PST
today.  That was the first place I checked.

Sorry and thanks,

ed

"Chris D. Faulhaber" wrote:

 On Sun, 30 Jan 2000, Edwin Culp wrote:

  I make a new world today after reinstalling xinstall and thought that
  along with recompiling my applications that are having problems that I
  assume started with the c++ compiler change, but I have recompiled
  several applications and still have the errors.
 
  If someone would tell me what I am doing wrong.  This is from the latest
  version of mysql that I just compiled.
 
  Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
  symbol
  "_vt$9exception"
 

 Please read the first 2124 entry of src/UPDATING.

 -
 Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]
 
 FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: libstdc++.so.3

2000-01-30 Thread Edwin Culp

I just got the new UPDATING and I seem to have done everything.  Until I built
xinstall, I wasn't able to make world, made a new kernel and rebooted and built
a new version of mysql and am still getting the error.  I'm going to build a
new world, just in case my cvsup timing was bad.

Thanks a lot for your help,

ed

Edwin Culp wrote:

 Looks like I have to cvsup again, it's not in my UPDATING from 11:40 PST
 today.  That was the first place I checked.

 Sorry and thanks,

 ed

 "Chris D. Faulhaber" wrote:

  On Sun, 30 Jan 2000, Edwin Culp wrote:
 
   I make a new world today after reinstalling xinstall and thought that
   along with recompiling my applications that are having problems that I
   assume started with the c++ compiler change, but I have recompiled
   several applications and still have the errors.
  
   If someone would tell me what I am doing wrong.  This is from the latest
   version of mysql that I just compiled.
  
   Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined
   symbol
   "_vt$9exception"
  
 
  Please read the first 2124 entry of src/UPDATING.
 
  -
  Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]
  
  FreeBSD: The Power To Serve   -   http://www.FreeBSD.org

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message