Re: buildworld across signal changes not quite right
Mark Murray wrote: I'm not sure how to fix this problem. Unlike our other build tools, perl is not designed to be able to be cross-built: It builds bits of itself and assumes they can be safely executed to build other bits. Perl is hugely fragile; cross-building it is a big PITA. If you have any smart ideas, I'm all ears. I haven't paid any special attention to it yet. (I may have mentioned before that I hate the perl build). No, but it is so noted now :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld across signal changes not quite right
David Scheidt wrote: On Tue, 23 Nov 1999, David O'Brien wrote: Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current buildworld running on an older -current system now progresses much further - in fact it now completes :-). Actually, I've been seeing just the opposite. Before you could build a -CURRENT kernel and then the world. Now those with worlds from this past summer can't build today's world regardless of which of userland or kernel is built first. The upgrade from -STABLE is also broken because of this. The %expect stuff is blowing up. I haven't yet tried to see if building yacc and bison manually fixes things or not. It will. I will tomorrow, when I have access to the box, assuming my workload doesn't try to kill me first. (I hadn't reported it, because I haven't had time to investigate properly. ) Be prepared to fix gcc and dd too. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld across signal changes not quite right
Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current buildworld running on an older -current system now progresses much further - in fact it now completes :-). There are, however still a few problems - as far as I can tell, these are all related to the wrong version of perl being called whilst perl is being built in the " Building everything.." section. I'm not sure how to fix this problem. Unlike our other build tools, perl is not designed to be able to be cross-built: It builds bits of itself and assumes they can be safely executed to build other bits. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld across signal changes not quite right
Peter Jeremy writes: | Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current | buildworld running on an older -current system now progresses much | further - in fact it now completes :-). | | There are, however still a few problems - as far as I can tell, these | are all related to the wrong version of perl being called whilst perl | is being built in the " Building everything.." section. | | I'm not sure how to fix this problem. Unlike our other build tools, | perl is not designed to be able to be cross-built: It builds bits | of itself and assumes they can be safely executed to build other bits. Yes this is very tricky. I run into a lesser issue when switching from threaded perl to unthread perl. This is currently broken since it doesn't link with the just built libs. This is further complicated in that other things sometimes need to find out how perl was built by asking perl. An example is vi with perl support which is also broken under threads. I can't see an obvious around this except to build a "build tools" version for use during the build and then a final version. An issue with this would be how to generate the config.h for the build platform since we currently have those pre-made for our target platforms. This doesn't address the issue of perl needing to report how it was built. I have sent in fixes for the 2 threaded perl issues. Doug A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
