make release problem
I had earlier written (to deafening silence) that I had been unable to build a release from current. Buildworlds worked OK, but make release didn't. I have since figured out what was not working, but this leads to another question. On my particular box, I don't have a whole lot of room on /usr, so I was building the world on /home, e.g. export MAKEOBJDIRPREFIX=/home/current. The world would build, but make release died compiling the boot crunch. There are a slew of derived files in /bin/sh - yacc output and such - that are not found. I discovered that just symlinking /usr/obj to the right place, and not setting MAKEOBJDIRPREFIX works just fine. I made a shot at trying to fix this, but quite frankly I must agree with the comment in the release Makefile - "You are not expected to like this." Is this considered a bug worth fixing? If not, at least this will be in the archive for the next confused person... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. You make it sound like a new thing - the release process has required the vn device for years. I would suggest that this driver be added to "GENERIC". For It's already dynamically loadable now. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. You make it sound like a new thing - the release process has required the vn device for years. Jordan, Thanks for your time. I guess I need to rephrase my comment I've done a dozen or so "make releases" this year. Until last week (or so), I didn't have nor need the "vn" driver in my kernel. Now release fails without it. Let me just suggest that something is (or was) somewhat broken. Best Regards, Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
In message [EMAIL PROTECTED], Mike Smith writes: In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. What do you mean "now"? It's _always_ been required. I actually think you could still do it with real floppies up until the point where we went to two-floppy install... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make release problem
In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. I would suggest that this driver be added to "GENERIC". For what it's worth, I added the driver to my kernel, rebooted, and completed the make release. Thanks all. Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. What do you mean "now"? It's _always_ been required. I would suggest that this driver be added to "GENERIC". For what it's worth, I added the driver to my kernel, rebooted, and completed the make release. vnconfig should just load the KLD; if this doesn't work, you can load it manually. Rebuilding a kernel is not required (and shouldn't be). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
In [EMAIL PROTECTED] Mike Smith [EMAIL PROTECTED] wrote: In trying to build "make release" today, I discovered that the "vn" driver is required now to build the boot floppies. What do you mean "now"? It's _always_ been required. I would suggest that this driver be added to "GENERIC". For what it's worth, I added the driver to my kernel, rebooted, and completed the make release. vnconfig should just load the KLD; if this doesn't work, you can load it manually. Rebuilding a kernel is not required (and shouldn't be). Some care must be taken when cross-building release - f.e. building 4.0-STABLE on the CURRENT system. Loading the KLD by vnconfig will use the newly build module in the chrooted environment i.e. 4.0-STABLE module while the kernel is CURRENT. So the module must be IN before to start 'make release'. N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release problem
Curious. I've done several (say a dozen) make release builds in the last 4 months of 4.0-CURRENT 5.0-CURRENT. The previous one was about 2 weeks ago. I've never had "vn" in my kernel, nor had a problem. Maybe something in the latest "loadable kernel modules" synchronization/version control changes have prevented automatic loading? In any event, I've never had this trouble before. For what it's worth, today after I got "make world" to work, I rebuilt my kernel did a make release (for my other machines). I had to add "vn" to my kernel for the first time to get "release" to work. You mileage may vary Kent To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
