[install-tools stage in Makefile.inc1] (was: Re: 3.4-4.0 ... *almost* ...)
On Wed, Feb 02, 2000 at 02:40:06PM -0400, The Hermit Hacker wrote: Been following the thread, and dove in today to do it. Remembered to do the 'xinstall' upgrade, ps and all the 'kvm related' utils work great ... now, make installworld fails at: === lib/libcom_err/doc install-info --quiet --defsection="Programming development tools." --defentry="* libcom_err: (com_err).A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Source tree is as of Feb 1st, so only 24hrs old, but I don't recall seeing anything go throughthe list concerning the above ... Help? :) On Wed, Feb 02, 2000 at 03:14:17PM -0500, Bill Fumerola wrote: Without looking at the specifics, I'd say that libcom_err depends on one of the new features of install-info (and the new version hasn't been merged from current). yet another thing to add to the bootstrap tools (or whatever they've called, I haven't followed the naming convention thread..) texinfo is already in bootstrap tools. The problem is that we do not have such a thing like `install' tools. Apparently, every tool we are using at installworld stage, should be compiled `static' at buildworld stage, and then these tools should be used at installworld. Among these tools, there should be at least xinstall and install-info. On Wed, Feb 02, 2000 at 09:16:26PM +0100, Alexander Langer wrote: As obrien suggested: cd /usr/src make -k installworld make installworld works. For short: The old install-info didn't know this new option. go to /usr/src/gnu/usr.bin/texinfo/install-info and install the new isntall-info (make clean all install) and then restart make installworld. Everything is fine then. I suggested Warner to add this to UPDATING, but I got no response. I could MFC the -current texinfo into -stable, so installworld of -current would be possible from the latest -stable, but... Another possibility would be to add install-tools target to Makeinfo.inc1 to statically build install tools like xinstall and install-info, and use them at installworld stage. I will prepare the patch tomorrow, will test it on my -stable machine, and will then send it to -current. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [install-tools stage in Makefile.inc1] (was: Re: 3.4-4.0 ... *almost* ...)
Ruslan Ermilov wrote: texinfo is already in bootstrap tools. The problem is that we do not have such a thing like `install' tools. Apparently, every tool we are using at installworld stage, should be compiled `static' at buildworld stage, and then these tools should be used at installworld. Among these tools, there should be at least xinstall and install-info. Don't forget the cross platform installation issues. If the installworld is executed on the target machine with the host machine's build area mounted, then this works fine. If you have the target machine's root mounted on the host machine, you can't use anything out of the build area. I could MFC the -current texinfo into -stable, so installworld of -current would be possible from the latest -stable, but... Another possibility would be to add install-tools target to Makeinfo.inc1 to statically build install tools like xinstall and install-info, and use them at installworld stage. I will prepare the patch tomorrow, will test it on my -stable machine, and will then send it to -current. The problem with install-info is not a linkage problem, but a feature change between the versions. So far I don't see a reason to to link it 'static'. I believe what needs to be done in this case is to ensure that install-info is installed before it is used. I suspect that a bit of careful addition of early installs in the middle of installworld will solve this problem. Jim Bloom [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [install-tools stage in Makefile.inc1] (was: Re: 3.4-4.0 ... *almost* ...)
On Wed, Feb 02, 2000 at 05:22:28PM -0500, Jim Bloom wrote: Ruslan Ermilov wrote: texinfo is already in bootstrap tools. The problem is that we do not have such a thing like `install' tools. Apparently, every tool we are using at installworld stage, should be compiled `static' at buildworld stage, and then these tools should be used at installworld. Among these tools, there should be at least xinstall and install-info. Don't forget the cross platform installation issues. If the installworld is executed on the target machine with the host machine's build area mounted, then this works fine. If you have the target machine's root mounted on the host machine, you can't use anything out of the build area. Maybe we could play with INSTALL_ARCH (the architecture on which the installworld will be run, defaulting to the MACHINE_ARCH)? I could MFC the -current texinfo into -stable, so installworld of -current would be possible from the latest -stable, but... Another possibility would be to add install-tools target to Makeinfo.inc1 to statically build install tools like xinstall and install-info, and use them at installworld stage. I will prepare the patch tomorrow, will test it on my -stable machine, and will then send it to -current. The problem with install-info is not a linkage problem, but a feature change between the versions. So far I don't see a reason to to link it 'static'. I believe what needs to be done in this case is to ensure that install-info is installed before it is used. I suspect that a bit of careful addition of early installs in the middle of installworld will solve this problem. There are at least 2 reasons to link them static: 1. On -stable we have libc.so.3, on -current - libc.so.4. 2. DESTDIR is not always /, so these tools (if installed early) could be out of $PATH anyway. -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
