Re: Latest binutils import breaks Alpha cross compiles
Peter Wemm wrote: > I dont suppose you actually thought to go and have a look and see what the > problem is yourself, rather than assigning the work to somebody else? Nope, sorry. I hear the latest binutils break Alpha cross compilation. My fix is to back out the changes locally, and not use them. Basically, instead of fixing the brokeness, I chose to not break the fixedness. My recommendation would be to revert the change until it can be imported as working code. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
usb breakage of LINT
Could a usb afficionado fix this? uhci.o: In function `uhci_idone': uhci.o(.text+0x1330): undefined reference to `uhci_dump_ii' uhci.o: In function `uhci_device_isoc_done': uhci.o(.text+0x2fab): undefined reference to `uhci_dump_ii' *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: many copies of make running while building a port...
On Wed, Jan 30, 2002 at 09:05:15PM +0100, Emiel Kollof wrote: >>I've had that happen when I put typos in /etc/make.conf (i.e. syntax >>errors or HAVE_/WANT_ variables that don't belong there). > >Hmm, curious. The symptoms disappeared when I commented the line >USE_GCC30=TRUE out of my make.conf. I switched it on because I read on >the current@ list that someone enabled it and didn't have any problems... Umm, this may be a stupid question, but do you have gcc30 installed and have you verified that it works? -- Alan E "Please rush me my portable walrus cleaning kit! Yes I am over 18, but my IQ isn't." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: many copies of make running while building a port...
In the last episode (Jan 30), Emiel Kollof said:
> Dan Nelson heeft op woensdag 30 januari 2002 om 19:27 het volgende geschreven:
> >>Number of procs in top(1) shoot up into the ranges of 600+ procs (and
> >>usually defunct). Load average sometimes jumps up into the 100+ (I
> >>kid you not). I doubt that that is desired operation. I only started
> >>seeing this behavior when I switched over to CURRENT, but this mail
> >>is cc'd to ports@ too, just in case. It makes using portupgrade(1) as
> >>tense as a good thriller flick (will my system survive? The
> >>suspense!)
> >
> >I've had that happen when I put typos in /etc/make.conf (i.e. syntax
> >errors or HAVE_/WANT_ variables that don't belong there).
>
> Hmm, curious. The symptoms disappeared when I commented the line
> USE_GCC30=TRUE out of my make.conf. I switched it on because I read
> on the current@ list that someone enabled it and didn't have any
> problems...
>
> Is USE_GCC30 actually supported? Should I just keep my hands off
> that? Or will it be a valid knob to switch over in the near future?
That was me, actually. I forgot to mention that I had a local hack in
bsd.port.mk to fix a little recursion problem with USE_GCC30 :)
The problem is that USE_GCC30 really means "make this port depend on
gcc30, and set CC=gcc30". But adding that flag to /etc/make.conf makes
gcc30 depend on gcc30, so during the find-dependencies stage, you get
recursive makes. I added code for a WITH_GCC30 flag that simply sets
CC=gcc30 without adding the dependency, and put WITH_GCC30=YES in
/etc/make.conf.
--- bsd.port.mk 24 Jan 2002 01:15:03 - 1.397
+++ bsd.port.mk 30 Jan 2002 21:10:24 -
@@ -916,6 +916,11 @@
BUILD_DEPENDS+=gcc30:${PORTSDIR}/lang/gcc30
MAKE_ENV+= CC=${CC} CXX=${CXX}
.endif
+.if defined(WITH_GCC30) && ${OSVERSION} < 500999
+CC=gcc30
+CXX= g++30
+MAKE_ENV+= CC=${CC} CXX=${CXX}
+.endif
.if defined(USE_LINUX)
RUN_DEPENDS+= ${LINUXBASE}/etc/redhat-release:${PORTSDIR}/emulators/linux_base
--
Dan Nelson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: AMD AGP Bug
Actually FreeBSD does make use of them, but in a way that doesn't cause a problem. Ken On Wed, 30 Jan 2002, David Malone wrote: > On Wed, Jan 30, 2002 at 12:13:07PM -0500, Cameron, Frank wrote: > > Has this issue been addressed in FreeBSD: > > > > http://www.geocrawler.com/lists/3/Linux/35/175/7626960/ > > http://slashdot.org/article.pl?sid=02/01/24/1910227&mode=thread > > This is believed not to have any impact on FreeBSD because FreeBSD > doesn't make much use of large pages. See Terry Lambert's post > to freebsd-current on 21st Jan for more details. > > David. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMD AGP Bug
You should check the archives of the FreeBSD mailing lists before sending a message to 4 of the lists. This quiestion has been answered several times on the FreeBSD lists. The answer is that this isn't even really an AMD AGP bug, it's a bug in the way linux handles mapping it's AGP memory. FreeBSD isn't affected by this at all. Ken On Wed, 30 Jan 2002, Cameron, Frank wrote: > Has this issue been addressed in FreeBSD: > > http://www.geocrawler.com/lists/3/Linux/35/175/7626960/ > http://slashdot.org/article.pl?sid=02/01/24/1910227&mode=thread > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: many copies of make running while building a port...
Dan Nelson heeft op woensdag 30 januari 2002 om 19:27 het volgende geschreven: >> Number of procs in top(1) shoot up into the ranges of 600+ procs (and >> usually defunct). Load average sometimes jumps up into the 100+ (I >> kid you not). I doubt that that is desired operation. I only started >> seeing this behavior when I switched over to CURRENT, but this mail >> is cc'd to ports@ too, just in case. It makes using portupgrade(1) as >> tense as a good thriller flick (will my system survive? The >> suspense!) > > I've had that happen when I put typos in /etc/make.conf (i.e. syntax > errors or HAVE_/WANT_ variables that don't belong there). > Hmm, curious. The symptoms disappeared when I commented the line USE_GCC30=TRUE out of my make.conf. I switched it on because I read on the current@ list that someone enabled it and didn't have any problems... Is USE_GCC30 actually supported? Should I just keep my hands off that? Or will it be a valid knob to switch over in the near future? Cheers, Emiel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest binutils import breaks Alpha cross compiles
On Wed, Jan 30, 2002 at 07:32:29PM +0100, Wilko Bulte wrote: > On Wed, Jan 30, 2002 at 09:13:13AM -0800, David O'Brien wrote: > > On Wed, Jan 30, 2002 at 08:20:39AM -0800, Peter Wemm wrote: > > > That's easy to say when signing up somebody else to do the work. > > > > > > Seriously though, in spite of pretending otherwise, i386 *is* our reference > > > platform, and the "other" platforms require people with the hardware and > > > interest to keep it "alive". > > ... Not to forget knowledge and time. > > > If there isn't enough critical mass to keep it going, then it is dead > > > by definition. > > > > This is my current feeling -- that Alpha 5-CURRENT no long has any > > critical mass. Thus it isn't worth the time or trouble. I'm would not call it dead only because it's always behind development. The latest alpha-current I'm running is nearly a month old - just because I always want to see a stable i386 before which I havn't seen for the last weeks. Sorry - I can't spend my time on alpha *and* machine independ bugs. > > My interests have moved over to sparc64 and x86-64 where I believe there Many alpha bugs and problems are there because of LP64 not because of alpha - other LP64 platforms will put LP64 into a much stronger position and help alpha a lot. I was always interested in FreeBSD-alpha because of having more than 4G memory and more than 4G address space - mostly the later. None is working - Memory is limited to 2G and increasing MAXDSIZ to big values is simply broken. Not ashtonishing that there is no big interest for anyoone to use FreeBSD-alpha in production - you can have these limits cheaper and without the bug troubles using Intel hardware. I always been sorrowed to run an FreeBSD-alpha as a cvsup server. > For x86-64 I see the point, sparc64 is not something I would want to spend > any time on (no disrespect to the sparc64 folks, I just don't think sparc > will have any great momentum). > > > will be a much larger following. It is shame after I've spent several > > thousand $$ on Alpha hardware over the past three years. That's what makes me still beleave in FreeBSD-alpha. Alpha is the cheapest 64 bit platform available. Think a moment on what you have paid for your sun labeled symbios. > And Alpha hardware is so much nicer than the x86 crap out there :( The same goes for sparc64 compared to x86. And sparc64 has a better future from the hardware perspective. I can understand why people are looking forward to sparc64. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP: login(1) PAMified
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: > Log: > Still with asbestos longjohns on, completely PAMify login(1) and remove > code made redundant by various PAM modules (primarily pam_unix(8)). > > Sponsored by: DARPA, NAI Labs This commit and the ones immediately preceding and following it strip most of the authentication logic out of login(1) and moves it into various PAM modules. Provided that your PAM library is up to date and you have etc/pam.d/login rev 1.7 (mergemaster is your friend!), login(1) should behave just like it used to. There's still a chance that something will crop up, though, so I'd recommend against upgrading systems you can't easily boot into single-user mode to fix a broken PAM config. If you run into trouble you can't get out of on your own, contact me by mail or on IRC (EvilDES on EFNet) and I'll try to figure it out ASAP. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest binutils import breaks Alpha cross compiles
On Wed, Jan 30, 2002 at 09:13:13AM -0800, David O'Brien wrote: > On Wed, Jan 30, 2002 at 08:20:39AM -0800, Peter Wemm wrote: > > That's easy to say when signing up somebody else to do the work. > > > > Seriously though, in spite of pretending otherwise, i386 *is* our reference > > platform, and the "other" platforms require people with the hardware and > > interest to keep it "alive". > ... > > If there isn't enough critical mass to keep it going, then it is dead > > by definition. > > This is my current feeling -- that Alpha 5-CURRENT no long has any > critical mass. Thus it isn't worth the time or trouble. > > My interests have moved over to sparc64 and x86-64 where I believe there For x86-64 I see the point, sparc64 is not something I would want to spend any time on (no disrespect to the sparc64 folks, I just don't think sparc will have any great momentum). > will be a much larger following. It is shame after I've spent several > thousand $$ on Alpha hardware over the past three years. And Alpha hardware is so much nicer than the x86 crap out there :( W/ -- | / o / /_ _ email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte FreeBSD core team secretary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: many copies of make running while building a port...
In the last episode (Jan 30), Emiel Kollof said: > Just a question: It seems while building a port, the ports system > somehow spawns hundreds and hundreds of copies of make (even so much > that they start hitting system limits). What's causing it, and how do > I make it stop doing that. > > Number of procs in top(1) shoot up into the ranges of 600+ procs (and > usually defunct). Load average sometimes jumps up into the 100+ (I > kid you not). I doubt that that is desired operation. I only started > seeing this behavior when I switched over to CURRENT, but this mail > is cc'd to ports@ too, just in case. It makes using portupgrade(1) as > tense as a good thriller flick (will my system survive? The > suspense!) I've had that happen when I put typos in /etc/make.conf (i.e. syntax errors or HAVE_/WANT_ variables that don't belong there). -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMD AGP Bug
On Wed, Jan 30, 2002 at 12:13:07PM -0500, Cameron, Frank wrote: > Has this issue been addressed in FreeBSD: > > http://www.geocrawler.com/lists/3/Linux/35/175/7626960/ > http://slashdot.org/article.pl?sid=02/01/24/1910227&mode=thread This is believed not to have any impact on FreeBSD because FreeBSD doesn't make much use of large pages. See Terry Lambert's post to freebsd-current on 21st Jan for more details. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Latest binutils import breaks Alpha cross compiles
On Wed, Jan 30, 2002 at 08:20:39AM -0800, Peter Wemm wrote: > That's easy to say when signing up somebody else to do the work. > > Seriously though, in spite of pretending otherwise, i386 *is* our reference > platform, and the "other" platforms require people with the hardware and > interest to keep it "alive". ... > If there isn't enough critical mass to keep it going, then it is dead > by definition. This is my current feeling -- that Alpha 5-CURRENT no long has any critical mass. Thus it isn't worth the time or trouble. My interests have moved over to sparc64 and x86-64 where I believe there will be a much larger following. It is shame after I've spent several thousand $$ on Alpha hardware over the past three years. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
AMD AGP Bug
Has this issue been addressed in FreeBSD: http://www.geocrawler.com/lists/3/Linux/35/175/7626960/ http://slashdot.org/article.pl?sid=02/01/24/1910227&mode=thread To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weirdness in building -CURRENT today
>Date: Wed, 30 Jan 2002 18:31:14 +0200 >From: Ruslan Ermilov <[EMAIL PROTECTED]> > stage 2: cleaning up the object tree >>-- >>... >>===> lib/libc >>"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a >>"/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a >>"/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a >>make: fatal errors encountered -- cannot continue >>*** Error code 1 >Should be fixed in the attached commit [src/sys/sys/stscall.mk revision >1.53 -- dhw]. Aye; it's certainly past the trouble-spot now -- thanks to both of you! Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weirdness in building -CURRENT today
On Wed, Jan 30, 2002 at 07:41:51AM -0800, David Wolfskill wrote: > >Date: Wed, 30 Jan 2002 17:02:07 +0200 > >From: Ruslan Ermilov <[EMAIL PROTECTED]> > > > >> stage 2: cleaning up the object tree > >> >-- > >> >... > >> >===> lib/libc > >> >"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a > >> >"/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a > >> >"/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a > >> >make: fatal errors encountered -- cannot continue > >> >*** Error code 1 > > >You probably have some locally modified src/ makefiles, > >or some crap in /etc/make.conf. > > Thanks for the suggestions. The locally-modified files I have on the > laptop are: > Should be fixed in the attached commit. -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --- Begin Message --- bde 2002/01/30 07:14:25 PST Modified files: sys/sys syscall.mk Log: Regenerate just this file after unbreaking makesyscalls.sh. The previous commit broke the world in libc. Revision ChangesPath 1.53 +1 -1 src/sys/sys/syscall.mk --- End Message ---
Re: Latest binutils import breaks Alpha cross compiles
Terry Lambert wrote: > David O'Brien wrote: > > > After the latest binutils import, attempts to cross-compile > > > Alpha fail at the cross-tools stage of buildworld as shown > > > below. Please also note sed(1) complaints about nonexistent > > > ldscripts/ files. I suspect that "normal" alpha worlds may > > > be broken as well, but I can't tell for sure. > > > > I am sure it probably is. There is a lack of developers using -current > > on Alpha's that progress on i386, IA64, x86-64, and sparc64 cannot be > > held back. I will fix the Alpha problems when I get a chance, but it may > > be a week. > > I know: add cross compilation for Alpha to your regression > on i386, IA84, x86-64, or sparc64, and that will catcth > things like this in the future, without you needing to have > Alpha hardware, and without you orphaning it as a result of > your changes. That's easy to say when signing up somebody else to do the work. Seriously though, in spite of pretending otherwise, i386 *is* our reference platform, and the "other" platforms require people with the hardware and interest to keep it "alive". This is the same with alpha as ia64, sparc64, powerpc, mips, x86-64 etc. If there isn't enough critical mass to keep it going, then it is dead by definition. Witness the mips port, it pretty much never made it to square one. I've done my bit over the last 6 months to keep the alpha alive (ported KSE phase 1 to alpha as well as 3 other platforms that I knew little to nothing about). I dont suppose you actually thought to go and have a look and see what the problem is yourself, rather than assigning the work to somebody else? Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weirdness in building -CURRENT today
>Date: Wed, 30 Jan 2002 17:02:07 +0200
>From: Ruslan Ermilov <[EMAIL PROTECTED]>
>> stage 2: cleaning up the object tree
>> >--
>> >...
>> >===> lib/libc
>> >"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a
>> >"/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a
>> >"/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a
>> >make: fatal errors encountered -- cannot continue
>> >*** Error code 1
>You probably have some locally modified src/ makefiles,
>or some crap in /etc/make.conf.
Thanks for the suggestions. The locally-modified files I have on the
laptop are:
Index: contrib/libpcap/gencode.c
Index: include/Makefile
Index: sys/dev/an/if_aironet_ieee.h
Index: sys/dev/an/if_an.c
Index: sys/dev/an/if_anreg.h
Index: sys/dev/ar/if_ar.c
Index: sys/dev/sound/pci/maestro.c
Index: sys/dev/sound/pci/maestro_reg.h
Index: sys/dev/sound/pcm/buffer.c
Index: sys/dev/sound/pcm/buffer.h
Index: sys/dev/sound/pcm/channel.c
Index: sys/dev/sr/if_sr.c
Index: usr.sbin/ancontrol/ancontrol.8
Index: usr.sbin/ancontrol/ancontrol.c
Index: usr.sbin/ppp/Makefile
In the case of include/Makefile, the difference is appending dev/an to
LSUBDIRS; in the case of usr.sbin/ppp/Makefile, the difference is
specification of a fully-qualified path for m4 on line 26.
The non-comments I have in /etc/make.conf are:
g1-7(5.0-CUR)[12] grep -v '^#' /etc/make.conf
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
COMPAT22= yes
COMPAT3X= yes
COMPAT4X= yes
PRINTERDEVICE= ps
HAVE_MOTIF= yes
USA_RESIDENT= YES
FORCE_PKG_REGISTER=YES
XFREE86_VERSION=4
WITH_PNG_MMX=YES
SENDMAIL_MC=/etc/mail/laptop.mc
g1-7(5.0-CUR)[13]
The thing that's puzzling me is that I've been tracking -CURRENT (as
well as -STABLE) daily for a while, successfully. And looking through
the archive of cvs-all, I don't see anything obvious within the last
couple of days. ("Last couple of days" vs. "last day" because I'm
acutely aware of the effect where a change can go in OK, but can break
during the next build. The gawk vs. one-true-awk incident is one such
case in recent memory, for example.)
Here's my recent CVSup history, in case it's of interest or value:
freebeast(5.0-CUR)[5] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Sat Jan 26 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Jan 26 04:37:34 PST 2002
CVSup begin from cvsup14.freebsd.org at Sun Jan 27 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Sun Jan 27 03:54:59 PST 2002
CVSup begin from cvsup14.freebsd.org at Mon Jan 28 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Mon Jan 28 04:38:31 PST 2002
CVSup begin from cvsup14.freebsd.org at Tue Jan 29 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Jan 29 03:56:22 PST 2002
CVSup begin from cvsup14.freebsd.org at Wed Jan 30 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Wed Jan 30 03:53:49 PST 2002
freebeast(5.0-CUR)[6]
(And yes, save for the last entry, I built both -STABLE and -CURRENT
after each CVSup. I got today's -STABLE built OK, too -- both on the
laptop and the build machine.)
Thanks,
david(links to my resume at http://www.catwhisker.org/~david)
--
David H. Wolfskill [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: telnetd broken in -CURRENT
> On Wed, Jan 30, 2002 at 01:47:24PM +, Mark Murray wrote: > > No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked > > against Heimdal. > > > > I'm testing the fix, and will commit in a day or two. > > OK, great. I assume you'll import it on the vendor branch? Yup! M -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Weirdness in building -CURRENT today
On Wed, Jan 30, 2002 at 06:33:43AM -0800, David Wolfskill wrote: > >Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST) > >From: David Wolfskill <[EMAIL PROTECTED]> > > >cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e > >tc/rc,v > >freebeast(4.5-STA)[2] > > That, at least, did not occur on my laptop. > > > stage 2: cleaning up the object tree > >-- > >... > >===> lib/libc > >"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a > >"/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a > >"/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a > >make: fatal errors encountered -- cannot continue > >*** Error code 1 > > That, however, did. > > > Guidance, hints, etc. cheerfully accepted. :-} > You probably have some locally modified src/ makefiles, or some crap in /etc/make.conf. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, 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: Weirdness in building -CURRENT today
>Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST) >From: David Wolfskill <[EMAIL PROTECTED]> >cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e >tc/rc,v >freebeast(4.5-STA)[2] That, at least, did not occur on my laptop. stage 2: cleaning up the object tree >-- >... >===> lib/libc >"/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a >"/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a >"/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a >make: fatal errors encountered -- cannot continue >*** Error code 1 That, however, did. Guidance, hints, etc. cheerfully accepted. :-} Thanks, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weirdness in building -CURRENT today
I think today is going to be "one of those days" :-( The first hint was after I built today's -STABLE, I then fired up a "cvs update" against my -CURRENT sources, and got: Script started on Wed Jan 30 05:12:16 2002 freebeast(4.5-STA)[1] cd /S4/usr/src && cvs update^M cvs update: Updating . cvs update: Updating bin cvs update: Updating bin/cat ... U etc/printcap U etc/profile U etc/protocols cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e tc/rc,v freebeast(4.5-STA)[2] I looked around at the results from "cvs log etc/rc" and 1.293 was the last revision I could see, so I don't know why it was trying to find 1.294. I tried removing src/etc/rc & re-starting the "cvs update", and the process then seemed to go to completion without further incident. I then re-booted the machine to run (yesterday's) -CURRENT, and started the build process... which died rather soon. Doing it again without -j8 showed: >>> stage 2: cleaning up the object tree -- ... ===> lib/libc "/usr/src/share/mk/bsd.lib.mk", line 184: Inconsistent operator for libc.a "/usr/src/share/mk/bsd.lib.mk", line 192: Inconsistent operator for libc_p.a "/usr/src/share/mk/bsd.lib.mk", line 224: Inconsistent operator for libc_pic.a make: fatal errors encountered -- cannot continue *** Error code 1 Ummm... OK; this doesn't look especially good. bsd.lib.mk hasn't been modified since 04 December, at revision 1.100 (bde). I think I could use a bit of guidance at this point. Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: telnetd broken in -CURRENT
On Wed, Jan 30, 2002 at 01:47:24PM +, Mark Murray wrote: > No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked > against Heimdal. > > I'm testing the fix, and will commit in a day or two. OK, great. I assume you'll import it on the vendor branch? -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: telnetd broken in -CURRENT
> On Tue, Jan 29, 2002 at 06:38:57PM -0800, Terry Lambert wrote: > > "Jacques A. Vidrine" wrote: > > > Meanwhile, do yourself a favor and use the Heimdal port if you want > > > Heimdal Kerberos. > > > > I think he cares more about telnet than Heimdal. > > Do we install the Heimdal telnetd as the default telnetd in -CURRENT? > I didn't think that we did. No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked against Heimdal. I'm testing the fix, and will commit in a day or two. M -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: telnetd broken in -CURRENT
On Tue, Jan 29, 2002 at 06:38:57PM -0800, Terry Lambert wrote: > "Jacques A. Vidrine" wrote: > > Meanwhile, do yourself a favor and use the Heimdal port if you want > > Heimdal Kerberos. > > I think he cares more about telnet than Heimdal. Do we install the Heimdal telnetd as the default telnetd in -CURRENT? I didn't think that we did. Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
2nd European BSD Conference
[sorry for people also on -announce getting this twice, I mail this here since I think it's interesting for cutting-edge users] Announcement and Call for Papers 2nd European BSD Conference November, 2002 Amsterdam, The Netherlands A conference organized by Stichting EuroBSDCon OVERVIEW The Berkeley Software Distributions (BSDs) represent one of the oldest and most vigorous streams of Open Source development. Together, OpenBSD, FreeBSD, NetBSD, Darwin, and BSD/OS represent millions of servers and desktops. The BSDs have long been part of the backbone of the Internet, in everything from embedded applications to large server installations, and will soon be widely deployed on consumer desktops. If you want to develop cutting-edge network applications, then the European BSD conference is the place to be. Meet all the movers and shakers of the BSD community, and learn how you can use BSD as part of your enterprise-grade solutions. This second European BSD conference will feature one day of tutorials and two days of technical sessions. The combination of technical tracks, invited talks, tutorials, and Birds-of-a-Feather sessions provides an opportunity for people of all experience levels to learn from BSD experts, professionals with real world experience, and industry leaders. The official language at the conference will be English. The exact date of the conference will be announced on the website. TUTORIAL PROGRAM (1 day) On the first day of the conference, a selection of practical, problem- solving, in-depth tutorials will be presented to you by the most authoritative, popular and widely acclaimed speakers in the field. If you're interested in presenting a tutorial or would like to share ideas about what would make a terrific tutorial, please contact the Program Committee at [EMAIL PROTECTED] TECHNICAL CONFERENCE (2 days) The next two days will offer comprehensive technical sessions, including keynote address, presentations of refereed papers and invited talks. Join peers and gurus during the enjoyable social event. The European BSD conference seeks original and innovative papers about the applications, architecture, implementation, performance and security of BSD-derived operating systems. Papers that analyze problem areas and draw important conclusions from practical experience are especially welcome. Presentations are being solicited in areas including but not limited to: * BSD kernel hacking * Embedded BSD application development and deployment * Device drivers * IPv6 deployment on BSD * BSD and security (Network Intrusion Detection Systems, Firewalls, VPNs, practical cryptography, auditing and computer forensics) * High performance networking * System and network performance tuning * Innovative BSD system administration tools and techniques * Running BSD on your toaster REFEREED PAPER SUBMISSIONS Papers for the technical sessions will be reviewed by the program committee. An award will be given at the conference for the best paper in this track. An extended abstract is required for the paper selection process. Abstracts must be submitted through the web form on http://www.eurobsdcon2002.org/. Abstracts accompanied by non-disclosure agreement forms are not acceptable and will be returned unread. Authors of accepted submissions must provide a final paper for publication in the conference proceedings. These final papers are held in the highest confidence prior to publication in the conference proceedings. By agreeing to present your paper at the European BSD conference, you also give license to the conference organizers that it may be published on the BSD conference web site. IMPORTANT DATES Extended abstracts due: June 24, 2002 Notification to speakers: July 12, 2002 Final papers due: October 7, 2002 CONFERENCE ORGANIZERS Program chair <[EMAIL PROTECTED]> Walter Belgers, Giga Computer Consultant, NL Program Committee <[EMAIL PROTECTED]> Frank van der Linden, Wasabi Systems, NL Wim Vandeputte, KD85.com bvba, BE Paul Kranenburg, Erasmus University, NL Event Organization <[EMAIL PROTECTED]> Guido van Rooij, chairman, Madison Gurkha, NL Jos Jansen, treasurer, Snow bv, NL Walter Belgers, secretary, Giga Computer Consultant, NL Marielle Klatten, conference organizer, ICONIQ, NL Complete program and registration information will be available in July 2002. For questions not being answered at http://www.eurobsdcon2002.org/, please contact the Iconiq office by e-mail: [EMAIL PROT
Wirus w Twojej poczcie od aaltours@gdynia.mtl.pl
Uwaga Wirus! Z przykroscia informujemy, iz w twojej poczcie od "[EMAIL PROTECTED]" zostal wykryty wirus: 'W32/Klez-E' Zawirusowany email zostal zatrzymany! Jesli chcesz otrzymac owa korespondencje to prosmy o wyslanie emaila na adres: [EMAIL PROTECTED] z tematem: virus-20020130-8727 WYSLIJ (poczta zostanie przeslana wraz z wirusem) virus-20020130-8727 OCZYSC (poczta zostanie oczyszczona i przeslana) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
