Re: HELP!!! -CURRENT libtool problem.

1999-07-13 Thread David O'Brien
You're correct in that better awareness is almost definitely the key. Would you consider posting the -stable and -current port build results You can find the realtime results from http://bento.freebsd.org/ -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Nik Clayton
advocate type="devils" On Sun, Jul 11, 1999 at 08:13:37PM +0900, Daniel C. Sobral wrote: [snip] "Q: Why shouldn't I just go ahead and run -current? That's got all the latest stuff, right? [snip] If you can live with that, and think you have any compelling reason to run -current, read

Re: HELP!!! -CURRENT libtool problem.

1999-07-06 Thread Jeremy Lea
Hi, On Mon, Jul 05, 1999 at 04:04:46PM -0400, Nicolas Blais wrote: Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm not very impressed. I was expecting some bugs but not like that... Not the best way to start a message if you want to get responses. Also, the wrapping

Re: HELP!!! -CURRENT libtool problem.

1999-07-05 Thread Jordan K. Hubbard
Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm not very impressed. I was expecting some bugs but not like that... I don't see a problem with FreeBSD 4.0 so much as a problem with someone jumping beyond their abilities. :) Please, go back to 3.2-STABLE. 4.0-CURRENT is

Re: HELP!!! -CURRENT libtool problem.

1999-07-05 Thread David O'Brien
Also, before I removed 3.2 from my system, I made a little cpp hello world program and with GCC the binary was 8k. That same program was 40k with EGCS. Anyone know why? Look at the ``ldd'' output. libstdc++ is statically linked if you used the egcs port (which if you did this on 3.2 you