Re: can someone explain this change to bsd.lib.mk ?

2002-03-09 Thread Luigi Rizzo
On Fri, Mar 08, 2002 at 12:26:16PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Luigi Rizzo writes: : The attached portion of the 1.100 - 1.101 patch to src/share/mk/bsd.lib.mk ... : I wonder, how does a make world get around this problem : (so i can try to reproduce the 'fix' in

Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )

2002-03-09 Thread Doug Rabson
On Fri, 8 Mar 2002, Matthew Jacob wrote: And FWIW, alpha kernels on some Uniprocessor boxes freeze up. I managed to panic my 4-cpu 4100 yesterday with a 'make -j8 buildworld' I'm going to look at that today. -- Doug Rabson Mail: [EMAIL PROTECTED]

Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )

2002-03-09 Thread Chris Hedley
On Fri, 8 Mar 2002, Chris Hedley wrote: ... about a crash ... Just in case anyone needs to know, I had another couple of panics today when trying to newfs_msdos /dev/fd0, seems something in readdisklabel isn't too happy. Chris. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe

New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Kris Kennaway
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

gvim weird linkage

2002-03-09 Thread Vallo Kallaste
Hi Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function names, very weird. I'm unable to build working gvim either from ports or by hand, also doesn't matter is it newest version or older 6.0 release. First thought

Re: gvim weird linkage

2002-03-09 Thread Jacques A. Vidrine
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Hi Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function names, very weird. I'm unable to build working gvim either from ports or by hand, also

Re: gvim weird linkage

2002-03-09 Thread Vallo Kallaste
On Sat, Mar 09, 2002 at 07:39:00AM -0600, Jacques A. Vidrine [EMAIL PROTECTED] wrote: Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Hm, thanks for confirming, but I'm running the very latest -current as I

Re: gvim weird linkage

2002-03-09 Thread Simon Dick
On Sat, Mar 09, 2002 at 03:55:13PM +0200, Vallo Kallaste wrote: On Sat, Mar 09, 2002 at 07:39:00AM -0600, Jacques A. Vidrine [EMAIL PROTECTED] wrote: Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Hm,

Re: binutils (libintl.h) problem (was: weird binutils problem)

2002-03-09 Thread Hiten Pandya
Please verify my hypothesis by applying this patch: Index: contrib/binutils/bfd/sysdep.h === RCS file: /home/ncvs/src/contrib/binutils/bfd/sysdep.h,v retrieving revision 1.1.1.6 diff -u -r1.1.1.6 sysdep.h ---

Re: binutils (libintl.h) problem (was: weird binutils problem)

2002-03-09 Thread Hiten Pandya
--- David Wolfskill [EMAIL PROTECTED] wrote: I'm not obrien, but yes, that is exactly what it means. Hmm, but I haven't defined it anywhere, and trust me on that, as I cvsup'ed a clean copy of the 'src' tree today, an deleting the old one. __ Do

Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )

2002-03-09 Thread David W. Chapman Jr.
I'm able to compile kdelibs now, no problem as well as QT, but when I run configure on kdebase it locks my system up. I can switch terminals but that's it. It locks up on configure when detecting QT(I believe line 5612). The first time it did this I decided that was because I need to rebuild

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread David W. Chapman Jr.
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,

Re: gvim weird linkage

2002-03-09 Thread David O'Brien
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function What revision of port/editors/vim/Makefile do you have? To Unsubscribe: send mail to [EMAIL

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread David O'Brien
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

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread David O'Brien
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:

kern_linker.c rev. 1.75 and newer cause loading problem

2002-03-09 Thread Steve Kargl
Well, I finally have narrowed the problem down to Revision 1.75 Fri Feb 22 04:14:49 2002 UTC (2 weeks, 1 day ago) by arr Branch: MAIN Changes since 1.74: +1295 -1271 lines Diff to previous 1.74 (colored) - Massive style fixup. Reviewed by: mike Approved by: dfr To recap: root[202] cat

Re: gvim weird linkage

2002-03-09 Thread Vallo Kallaste
On Sat, Mar 09, 2002 at 09:55:50AM -0800, David O'Brien [EMAIL PROTECTED] wrote: On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function What

Re: gvim weird linkage

2002-03-09 Thread Vallo Kallaste
On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick [EMAIL PROTECTED] wrote: Any hints? Seems like some environment configuration problem or latent bug somewhere.. I just rebuild my current today and gvim has started working for me again now I did cvsup, world and new kernel, just in

Re: gvim weird linkage

2002-03-09 Thread Olivier Houchard
On Sat, Mar 09, 2002 at 10:41:32PM +0200, Vallo Kallaste wrote: On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick [EMAIL PROTECTED] wrote: Any hints? Seems like some environment configuration problem or latent bug somewhere.. I just rebuild my current today and gvim has started

A MUST for all IT-Executives!

2002-03-09 Thread www.it-report.co.uk
A MUST for all IT-Executives! In March 2002 the new, free it-REPORT has started for IT Executives with TOP-news, highlights and interesting topics from the sectors of eCommerce, Internet, Computer, Telecommunications etc (and so on). It will be sent to over 150.000 IT-Executives, free of

Re: gvim weird linkage

2002-03-09 Thread Vallo Kallaste
On Sat, Mar 09, 2002 at 09:42:07PM +0100, Olivier Houchard [EMAIL PROTECTED] wrote: I did cvsup, world and new kernel, just in case.. but it really doesn't matter. Same problem. You may try to compile vim with ./configure --disable-xim too. It worked for me. Tried without XIM support

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Kris Kennaway
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

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Will Andrews
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

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Robert Watson
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:

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Will Andrews
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.

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread Kris Kennaway
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

Upgrading to 5-CURRENT via sources

2002-03-09 Thread Lamont Granquist
So, I've got a CVS checkout of 5-CURRENT on my 4.5-STABLE box and I'd like to upgrade to a spare partition that I have on the machine (making it dual boot). Can I just do: make world DESTDIR=/mnt/tmp And then build + drop the kernel into place + reboot? To Unsubscribe: send mail to [EMAIL

Re: New i386 5.0 packages uploaded (and toolchain problems)

2002-03-09 Thread David O'Brien
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

Re: Preparing innocent users for -current

2002-03-09 Thread Murray Stokely
On Fri, Mar 08, 2002 at 04:55:29PM -0500, Garance A Drosihn wrote: One thing to keep in mind here is that this is still going to be a snapshot of -current, and not a production release of -stable. We want a snapshot that does not have any serious problems, but innocent users should still