Re: Totally lost
On Fri, Dec 10, 2004 at 08:23:40PM +, Mário Gamito wrote: Hi, When i install FreeBSD 5.3, libtool, automake and autoconf don't get installed. I upgrade the ports. After that is the total confusion. One program wants libtools version x, another, y ando so on. Some thing to automake and autoconf. How do i solve this mess ? I'm driving nuts :( Any help would be apreciated. I suggest breaking the problem(s) apart by starting with one single port you need; one generally found on many systems. But prior to that, tell us more or less where you are in the installation process for this particular machine; also tell us what this particular machine wil be used to do: home desktop, webserver, shell server, print server...or something else altogether. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Totally lost
Mário Gamito wrote: Hi, When i install FreeBSD 5.3, libtool, automake and autoconf don't get installed. I upgrade the ports. After that is the total confusion. One program wants libtools version x, another, y ando so on. Some thing to automake and autoconf. How do i solve this mess ? FreeBSD is cool enough to allow multiple versions of libtool and autoconf etc to be installed, just as you can have multiple versions of Perl. By default one version is used, but the others are used if you specify the version extension, eg. on my system, /usr/local/bin/autoconf is version 2.53, while I can get 2.59 or 2.13 by calling autoconf259 autoconf213 respectively, similar for the other autotools and libtool. Obviously, there is a reason for having multiple versions installed, namely because some ports still relies on old versions, while others requires features in new experimental versions. Unless the developers settle on one version of these tools, you will have multiple versions installed. If it really annoys you to see that they are there, they are AFAIK only used for compiling, linking etc. so once you have installed your system you can deinstall these programs. But, there is no need to, and they will be reinstalled when you try to upgrade your ports. It should only bother you if you are trying to write your own ports, or are doing other development. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Totally lost
Mário Gamito wrote: Well, actuallly, after i make a port upgrade with cvsup, i go to /usr/ports (there's) a Makefile there, and do a make install. That Makefile enters an endless loop asking for libtool 1.8 (i think this is the version), that it's not in the ports. You most certainly don't want to do that. I don't think the loop is endless, it's just very long as you will be trying to install all 11000+ ports. What you (should) do is: * upgrade the ports tree with 'cvsup ports-supfile' * then upgrade the packages you need, either by 1) go into the package directory under collection/pkg-name and type make make deinstall make install (assuming it was installed, since you want to upgrade) 2) run 'portupgrade pkg-name' note, that you may have to use the recursive flags -r and -R for this to succeed. BTW, what's the difference in using cvsup or portupdate to update the ports ? See above. cvsup only updates the ports tree, ie the make files needed to build the programs for your system, portupgrade (i guess you mean that and not portupdate) will build and upgrade installed ports, using the current ports tree makefiles and patches. This is so confusing, and i already read a lot about it. Mybe i'm simply dumb, but i'm a Linux system's administrator for years (i remember walking with Slackware in a pack of floppies, LOL :) ) Maybe you just read too much and need to let it settle. Happens to me sometimes. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Totally lost
Mário Gamito wrote: Hi, Well, actuallly, after i make a port upgrade with cvsup, i go to /usr/ports (there's) a Makefile there, and do a make install. I am not sure that you want to do this under what I consider normal circumstances. There is a target there for updating the tree via CVS if I'm reading it right, and a useful one for fetchindex. Most users probably don't want to make install the whole tree, and I'm not sure by reading the Makefile that you can, anyway. Maybe someone else can shed some light on that issue. That Makefile enters an endless loop asking for libtool 1.8 (i think this is the version), that it's not in the ports. BTW, what's the difference in using cvsup or portupdate to update the ports ? Do you mean portupgrade? (Or is portupdate the binary C. Percival type thing?) CVSup and CVS do similar things, but portupgrade is quite different. Keep in mind that the ports tree itself is simply a large directory tree of port skeletons, that is, Makefiles and patches that allow the system to automagically fetch, unzip, configure, compile, and install (and clean up after) software. Using CVSup (or CVS, or CTM, etc.) you simply grab the latest copies of the tree from the online repository. Portupgrade, on the other hand, checks your package database to see what's installed on your system and compares the version numbers to those in the (usually newly cvsupped) ports tree. It then does all the fetch-unzip-configure-compile-clean stuff for you, without you ever having to type much (if you do it right) and will, if desired, do the same thing recursively for all dependencies, etc. (I can only assume that if there's such a thing as 'portupdate', [and it does seem like it's coming if not already here] that it does a similar thing, only using precompiled binaries.) This is so confusing, and i already read a lot about it. Mybe i'm simply dumb, but i'm a Linux system's administrator for years (i remember walking with Slackware in a pack of floppies, LOL :) ) Heh, you can still fit PicoBSD on one ... ;-) Regards. Mário Gamito HTH, Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Totally lost
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Mário Gamito Sent: Saturday, December 11, 2004 4:16 To: Erik Norgaard Cc: [EMAIL PROTECTED] Subject: Re: Totally lost Hi, Well, actuallly, after i make a port upgrade with cvsup, i go to /usr/ports (there's) a Makefile there, and do a make install. That Makefile enters an endless loop asking for libtool 1.8 (i think this is the version), that it's not in the ports. BTW, what's the difference in using cvsup or portupdate to update the ports ? This is so confusing, and i already read a lot about it. Mybe i'm simply dumb, but i'm a Linux system's administrator for years (i remember walking with Slackware in a pack of floppies, LOL :) ) Regards. Mário Gamito Cvsup basically updates your port tree. By update I mean it updates the makefiles, Although it does not touch the already installed port binaries. When you run portupgrade, it parses through the makefiles of the already installed ports, check for dependencies and updates the port binaries if required. Regards S. Indian Institute of Information Technology Subhro Sankha Kar Block AQ-13/1, Sector V Salt Lake City PIN 700091 India smime.p7s Description: S/MIME cryptographic signature
Re: Totally lost
Mário Gamito [EMAIL PROTECTED] writes: Hi, When i install FreeBSD 5.3, libtool, automake and autoconf don't get installed. I upgrade the ports. After that is the total confusion. One program wants libtools version x, another, y ando so on. Some thing to automake and autoconf. How do i solve this mess ? I'm driving nuts :( Any help would be apreciated. The FreeBSD ports system is perfectly happy to install multiple versions of automake and autoconf for you, where that is necessary. It's also happy to upgrade them for you. What is your actual problem? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Totally lost
Hi, Well, actuallly, after i make a port upgrade with cvsup, i go to /usr/ports (there's) a Makefile there, and do a make install. That Makefile enters an endless loop asking for libtool 1.8 (i think this is the version), that it's not in the ports. BTW, what's the difference in using cvsup or portupdate to update the ports ? This is so confusing, and i already read a lot about it. Mybe i'm simply dumb, but i'm a Linux system's administrator for years (i remember walking with Slackware in a pack of floppies, LOL :) ) Regards. Mário Gamito Erik Norgaard wrote: Mário Gamito wrote: Hi, When i install FreeBSD 5.3, libtool, automake and autoconf don't get installed. I upgrade the ports. After that is the total confusion. One program wants libtools version x, another, y ando so on. Some thing to automake and autoconf. How do i solve this mess ? FreeBSD is cool enough to allow multiple versions of libtool and autoconf etc to be installed, just as you can have multiple versions of Perl. By default one version is used, but the others are used if you specify the version extension, eg. on my system, /usr/local/bin/autoconf is version 2.53, while I can get 2.59 or 2.13 by calling autoconf259 autoconf213 respectively, similar for the other autotools and libtool. Obviously, there is a reason for having multiple versions installed, namely because some ports still relies on old versions, while others requires features in new experimental versions. Unless the developers settle on one version of these tools, you will have multiple versions installed. If it really annoys you to see that they are there, they are AFAIK only used for compiling, linking etc. so once you have installed your system you can deinstall these programs. But, there is no need to, and they will be reinstalled when you try to upgrade your ports. It should only bother you if you are trying to write your own ports, or are doing other development. Cheers, Erik -- Mário Gamito Administração de sistemas e desenvolvimento Netual - Multimédia e Telecomunicações, Lda. Rua João Afonso, Nº1 3800-198 Aveiro - Portugal Tel. +351 234 371 431 / Fax. +351 234 371 438 E-mail: [EMAIL PROTECTED] www.netual.pt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
