Re: HELP!!! -CURRENT libtool problem.
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 mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
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 the handbook for further instructions. Sorry if this seems too harsh, but many people are just not used to the concept of a development tree available publicly, and think of it as the "latest version". It is *not* the latest version. When it is *ready*, it will be the latest version. Until then... read the above." Any other question? Q: I want to use this cool piece of software that's in the FreeBSD ports system. But I can't build it on my 3.x-stable system. Why not? A: Ah, sorry. The ports system only targets -current, trying to get it to work with -stable is too much work. If you want to be sure of using the ports system successfully you need to be running -current. /advocate Or was this policy reversed recently and I didn't notice (always a likely possibility). [ And yes, I *know* the ports system relies on volunteers, and that if people can't be bothered to test their ports on a -stable system then there's not a lot we can do about it. But this does lead to the amusing situation (for various values of "amusing") where on one hand we're telling people not to use -current unless they really know what they're doing, but on the other hand we're (in some cases) preventing them from using a major piece of FreeBSD infrastructure which is expressly designed to make life easier for exactly the sort of people who should be running -stable. ] N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
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 on your e-mail editor is broken. Most of my stuff compiles great with EGCS except all my shared libraries that uses libtool like jpeglib and giflib. They both use libtool which for some odd reason was not installed on my system. If you had actually provided some useful information then maybe the problem could be determined, but I'd guess that your system is broken... The ports all work (although there is a problem for old libtool installations - which you don't have), and libtool will be installed by ports which need it. The same ports work on both -STABLE and -CURRENT, so I'd also guess that you messed up during the upgrade. Maybe an old bsd.port.mk somewhere? I also assume that if you fetched the package, then you are building from ports? If not, then don't fetch the package, go fetch libtool from a GNU mirror and build it manually (and do whatever patching is needed for 4.0). If you're not using ports, then you'll get even less help than if you have a problem with -CURRENT. Please help. I'm really desperate. Stick with -STABLE and packages. -Jeremy -- | "In this world of temptation, I will stand for what is right. --+-- With a heart of salvation, I will hold up the light. |If I live or if I die, if I laugh or if I cry, |in this world of temptation, I will stand." -Pam Thum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
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 a *development* version and you're expected to understand how to deal with things like applications breakage (including how to recompile libtool and any other components you may need) before doing anything as rash as running 4.0-current. I'm also sure this response will probably scare a few people off and garner stern rebukes from the newbie hand-holding folks, but it's honestly always been the case that -current is NOT for anyone but the advanced class students and we like it that way because we'd otherwise spend more time coaching people over the bumps than we did in actually working on -current and evolving FreeBSD significantly at all. Think of -current as an operating room where surgeons are actively working on a patient under anaesthesia - do you really want just anybody wandering in there to ask the doctors random questions while they work or do you maybe want to limit participation to only those with some prior medical training? I also make this point now and with such force because various signs and portents indicate that -current is about to become a dangerous place again for awhile, and a lot of people who really don't have the cojones to run -current are going to find this out rather abruptly and painfully. :-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
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 must have). -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
