Re: Is this LOST??
On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote: > I found the htonl implemention in libc for i386 is not sync with the > kern. > > sys use bswap for swaping the int. but libc still use xchg. > IS THIS LOST? It's because libc still supports 80386 which doesn't have bswap (introduced on the 486 IIRC). The kernel only supports 486+ unless you explicitly build an 80386 kernel, which won't use bswap for htonl(). -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is this LOST??
On Tue, May 04, 2004 at 09:04:53AM +0800, Deng XueFeng wrote: > > On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote: > > > I found the htonl implemention in libc for i386 is not sync with the > > > kern. > > > > > > sys use bswap for swaping the int. but libc still use xchg. > > > IS THIS LOST? > > > > It's because libc still supports 80386 which doesn't have bswap (introduced on > > the 486 IIRC). The kernel only supports 486+ unless you explicitly build an > > 80386 kernel, which won't use bswap for htonl(). > Since 5-current kernel do not support 80386. > why keep libc(5-current) support 80386? 5-current does support 80386, just not in the default GENERIC kernel. Kris pgp0.pgp Description: PGP signature
Re: Is this LOST??
Deng XueFeng wrote this message on Tue, May 04, 2004 at 09:04 +0800: > > the 486 IIRC). The kernel only supports 486+ unless you explicitly build an ^^^ > > 80386 kernel, which won't use bswap for htonl(). > Since 5-current kernel do not support 80386. > why keep libc(5-current) support 80386? because you can still run -current on an 80386, at least that's what I hear from bde. :) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is this LOST??
> On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote: > > I found the htonl implemention in libc for i386 is not sync with the > > kern. > > > > sys use bswap for swaping the int. but libc still use xchg. > > IS THIS LOST? > > It's because libc still supports 80386 which doesn't have bswap (introduced on > the 486 IIRC). The kernel only supports 486+ unless you explicitly build an > 80386 kernel, which won't use bswap for htonl(). Since 5-current kernel do not support 80386. why keep libc(5-current) support 80386? and if wanna 80386 support, 4-stable can do that. Sincerely, Deng XueFeng ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is this LOST??
Deng XueFeng <[EMAIL PROTECTED]> writes: > Since 5-current kernel do not support 80386. > why keep libc(5-current) support 80386? Set CPUTYPE and make world. See 'man make.conf' for details. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is this LOST??
> > On Sunday 02 May 2004 01:26 am, Deng XueFeng wrote: > > > I found the htonl implemention in libc for i386 is not sync with the > > > kern. > > > > > > sys use bswap for swaping the int. but libc still use xchg. > > > IS THIS LOST? > > > > It's because libc still supports 80386 which doesn't have bswap (introduced on > > the 486 IIRC). The kernel only supports 486+ unless you explicitly build an > > 80386 kernel, which won't use bswap for htonl(). > > Since 5-current kernel do not support 80386. > why keep libc(5-current) support 80386? The 5-current kernel *does* support 80386 -- you have to recompile your kernel to add 80386 support first. -- Matt Emmerton ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
