Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: > uname extracts the various strings it can report from the running kernel > using sysctl. Unless you have a faked uname, it will return the The cluster has used a faked out uname(1) for a long time. The problem turned out to be with its generation by the scripts. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 09:58:05AM -0800, David O'Brien wrote: > On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: > > The failures were caused by compiled utilities dumping core with sig11 > > or sig10 during compilation of the port. Toolchain people, please > > look into this; the error logs are at > > I am not sure we can say anything about the errors due to the 5.0 world > under a 4.5 kernel. Can you update just one of the slaves to very > -current and try some manual builds of the most problematic failing > ports? Yep, I'll try that next once the current build finishes. Kris msg35903/pgp0.pgp Description: PGP signature
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 07:30:21PM -0500, Robert Watson wrote: > uname extracts the various strings it can report from the running kernel > using sysctl. Unless you have a faked uname, it will return the > properties of the host non-chroot environment, rather than the chroot > environment. Increasingly, it's going to be harder and harder to run 5.0 > in a 4.x chroot, due to divergence in system calls, especially once > threaded applications start using KSE. Running 4.x in a 5.0 chroot should > (hopefully) continue to work fine. You are right. I made a thinko, and later realized it while talking to Kris. I was hoping nobody would notice... :) We are screwed if anybody uses sysctl() or sysctlbyname(), unless someone decides to allow us to change kernel variables and the like inside chroot() (or perhaps jail()).. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, 9 Mar 2002, Will Andrews wrote: > On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: > > This isn't good: > > > > http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log > > > > building TenDRA-4.1.2 on gohan17 > > in directory /x/tmp/5/chroot/31459 > > with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA > > maintained by: [EMAIL PROTECTED] > > build started at Sat Mar 9 00:37:43 GMT 2002 > > ... > > Operating system version = 4.4-STABLE > > > > I thought uname was faked out to return the proper value. > > I wonder if things like this could be one of the problems. > > More like, the port builds in a chroot which contains the environment of > a 5.0 world. So the chroot tarball for 5.0 being used here must be the > wrong one, or it's screwed up. uname extracts the various strings it can report from the running kernel using sysctl. Unless you have a faked uname, it will return the properties of the host non-chroot environment, rather than the chroot environment. Increasingly, it's going to be harder and harder to run 5.0 in a 4.x chroot, due to divergence in system calls, especially once threaded applications start using KSE. Running 4.x in a 5.0 chroot should (hopefully) continue to work fine. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: > This isn't good: > > http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log > > building TenDRA-4.1.2 on gohan17 > in directory /x/tmp/5/chroot/31459 > with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA > maintained by: [EMAIL PROTECTED] > build started at Sat Mar 9 00:37:43 GMT 2002 > ... > Operating system version = 4.4-STABLE > > I thought uname was faked out to return the proper value. > I wonder if things like this could be one of the problems. More like, the port builds in a chroot which contains the environment of a 5.0 world. So the chroot tarball for 5.0 being used here must be the wrong one, or it's screwed up. Thanks for pointing this out. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 10:00:10AM -0800, David O'Brien wrote: > On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: > > http://bento.freebsd.org/errorlogs/5-latest/ > > This isn't good: > > http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log > > building TenDRA-4.1.2 on gohan17 > in directory /x/tmp/5/chroot/31459 > with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA > maintained by: [EMAIL PROTECTED] > build started at Sat Mar 9 00:37:43 GMT 2002 > ... > Operating system version = 4.4-STABLE > > I thought uname was faked out to return the proper value. Hmm, I thought it was too..let me look into it. > I wonder if things like this could be one of the problems. Kris msg35899/pgp0.pgp Description: PGP signature
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: > http://bento.freebsd.org/errorlogs/5-latest/ This isn't good: http://bento.freebsd.org/errorlogs/5-latest/TenDRA-4.1.2.log building TenDRA-4.1.2 on gohan17 in directory /x/tmp/5/chroot/31459 with arguments: TenDRA-4.1.2.tgz /usr/ports/lang/TenDRA maintained by: [EMAIL PROTECTED] build started at Sat Mar 9 00:37:43 GMT 2002 ... Operating system version = 4.4-STABLE I thought uname was faked out to return the proper value. I wonder if things like this could be one of the problems. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: > The failures were caused by compiled utilities dumping core with sig11 > or sig10 during compilation of the port. Toolchain people, please > look into this; the error logs are at I am not sure we can say anything about the errors due to the 5.0 world under a 4.5 kernel. Can you update just one of the slaves to very -current and try some manual builds of the most problematic failing ports? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: > I've uploaded a new set of packages to ftp-master for -current on > i386; they should be picked up by the mirrors shortly. As I mentioned > in a previous mail, there were compilation problems which caused a > number of ports to fail, including qt2 and gnomelibs, meaning there > were no KDE or GNOME packages built (hey, at least it's a symmetric > failure!). QT built fine for me with a -current as of yesterday night, and so does kdelibs, but as I posted earlier kdebase locks up the system on configure, but I believe this is known as the "(Subject: Keyboard (quasi-)lockup running script)" or sounds similar. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
New i386 5.0 packages uploaded (and toolchain problems)
I've uploaded a new set of packages to ftp-master for -current on i386; they should be picked up by the mirrors shortly. As I mentioned in a previous mail, there were compilation problems which caused a number of ports to fail, including qt2 and gnomelibs, meaning there were no KDE or GNOME packages built (hey, at least it's a symmetric failure!). The failures were caused by compiled utilities dumping core with sig11 or sig10 during compilation of the port. Toolchain people, please look into this; the error logs are at http://bento.freebsd.org/errorlogs/5-latest/ I also tried upgrading to a more recent 5.0 snapshot in which to perform the builds, but it seems there have been syscall changes and you can no longer cheat and run a 5.0 world inside a chroot on a 4.x machine: for example, sh dies with signal 12. Perhaps I'll have to upgrade the cluster to 5.0 to do the package building after all, but that on its own won't fix the toolchain problems. Kris msg35881/pgp0.pgp Description: PGP signature
