Re: HEADS UP: i386 a.out binary users!
Peter Wemm wrote: You will need to either add: options COMPAT_AOUT to your kernel config when you next rebuild, or do a 'kldload aout' when you want to run an old a.out binary. Is this going to be turned on be default in the rc scripts, until such time as sysinstall is taught about asking the user the same way it asks the user about compatability packages or Linux emulation? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: perl busted, spins, ignores SIGKILL
On Wed, 4 Sep 2002, Thomas Quinot wrote: Le 2002-09-03, Lamont Granquist écrivait : i cvsup'd last night, and now i tried portupdate -a -f and debugging build problems with libtool i found that on my system i can make perl spin and consume 100% of a CPU just by: perl -pe s/foo/bar/g /tmp Any chance you have a /usr/local/bin/perl pointing back to /usr/bin/perl? Cf. PR bin/42418. yes, in fact i appear to have that very problem... that's a really annoying bug... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libmd bug on -CURRENT
On Fri, 6 Sep 2002, Bruce A. Mah wrote: If memory serves me right, Poul-Henning Kamp wrote: Good catch. I'm surprised the compiler doesn't whine. Thanks, and me too. Warnings are mostly turned off for not unimportant places like libraries since these places are too poorly written to compile without warnings. PS. Actually I'm surprised that nobody caught the problem in the past five months...this bug prevented release builds from 5-CURRENT hosts. Maybe I'm the only person crazy enough to try this. :-) This bug was caught in PR 42384. The fix in the PR is not so good. libmd is also broken for some cases involving pipes. IIRC, this is caused by the bogus st_size checks in the same function. st_size is only valid for regular files. The loop in the function fails to to terminate if read() returns 0, which can probably happen if the file shrinks underneath us. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sparc64 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === usr.bin/kdump In file included from ioctl.c:41: /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include/net/if_gre.h:93: field `gi_i' has incomplete type /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include/net/if_gre.h:137: field `mi' has incomplete type *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/usr.bin/kdump. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/usr.bin. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === usr.bin/kdump In file included from ioctl.c:18: /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include/netinet/ip.h:158: syntax error before n_long /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include/netinet/ip.h:161: syntax error before n_long *** Error code 1 Stop in /var/tmp/des/src/usr.bin/kdump. *** Error code 1 Stop in /var/tmp/des/src/usr.bin. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
New to -CURRENT
Just d/led the 5.0-CURRENT-20020813-JPSNAP.ISO from the snapshots.jp.freebsd.org. I installed it on a Dell Laptop Inspiron 5000 i needed support form my Xircom Cardbus Ethernet II 10/100. I heard the ACPI is still buggy. Wanted to check on that cuz i noticed the fan on the back isn't running. and i don't want it to burn up. Trying to get cvsup and all its dependencies installed right now so i can cvsup my source and try recompiling. Let me know if anyone wants any info from the system. Thank you Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Todays cvsup Current on kernel mkdep shows opt_cpu.h: No such file
After a successful make world, I got the following error on initiating buildkernel. mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I@/. ./include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/linux/../../ i386/linux/linux_dummy.c /usr/src/sys/modules/linux/../../compat/linux/linux_fil e.c /usr/src/sys/modules/linux/../../compat/linux/linux_getcwd.c /usr/src/sys/mo dules/linux/../../compat/linux/linux_ioctl.c /usr/src/sys/modules/linux/../../co mpat/linux/linux_ipc.c /usr/src/sys/modules/linux/../../i386/linux/linux_machdep .c /usr/src/sys/modules/linux/../../compat/linux/linux_mib.c /usr/src/sys/module s/linux/../../compat/linux/linux_misc.c /usr/src/sys/modules/linux/../../compat/ linux/linux_signal.c /usr/src/sys/modules/linux/../../compat/linux/linux_socket. c /usr/src/sys/modules/linux/../../compat/linux/linux_stats.c /usr/src/sys/modul es/linux/../../compat/linux/linux_sysctl.c /usr/src/sys/modules/linux/../../i386 /linux/linux_sysent.c /usr/src/sys/modules/linux/../../i386/linux/linux_sysvec.c /usr/src/sys/modules/linux/../../compat/linux/linux_util.c /usr/src/sys/modules /linux/../../i386/linux/linux_ptrace.c /usr/src/sys/modules/linux/../../compat/l inux/linux_uid16.c /usr/src/sys/modules/linux/../../i386/linux/imgact_linux.c /usr/src/sys/i386/linux/linux_sysvec.c:33:30: opt_kstack_pages.h: No such file o r directory /usr/src/sys/i386/linux/linux_ptrace.c:31:21: opt_cpu.h: No such file or directo ry mkdep: compile failed *** Error code 1 ed -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to buildworld (new record, 18)
On 07-Sep-2002 (20:22:42/GMT) Kris Kennaway wrote: My -CURRENT is pre-gcc_3.1, running very fine from early May. I'm in between some big update? Where I'm wrong? Have you read through UPDATING? Yes, more and more, after every cvsup. I added -DNO_WERROR without luck, I also found two PR speaking about wchar_t (31864 and 40084). There is something related to a new internal declaration I think. One moment, ... are you speaking about this? 20020510: Due to the way CVS works, it may not properly update src/contrib/gcc to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc and then do a cvs update. I'm about to remove contrib/gcc tree and cvsuping again... Thanks, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to buildworld (new record, 18)
On 07-Sep-2002 (21:00:28/GMT) Riccardo Torrini wrote: Have you read through UPDATING? Yes, more and more ... I added -DNO_WERROR without luck I also found two PR speaking about wchar_t (31864 and 40084). I'm about to remove contrib/gcc tree and cvsuping again... No, same error :( Any other ideas? === gnu/usr.bin/gperf/doc c++ -O2 -pipe-D__FBSDID=__RCSID -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc In file included from /usr/include/stdio.h:44, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.h:57, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc:21: /usr/include/sys/_types.h:71: declaration does not declare anything *** Error code 1 Thanks again, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Unable to buildworld (new record, 18)
On Sat, Sep 07, 2002 at 06:25:04PM +0200, Riccardo Torrini wrote: My -CURRENT is pre-gcc_3.1, running very fine from early May. I regularly build world and kernel (without installing them) every week. I'm in between some big update? Where I'm wrong? Have you read through UPDATING? Kris msg42721/pgp0.pgp Description: PGP signature
Re: Unable to buildworld (new record, 18)
In message: [EMAIL PROTECTED] Riccardo Torrini [EMAIL PROTECTED] wrote: No, same error :( Any other ideas? === gnu/usr.bin/gperf/doc c++ -O2 -pipe-D__FBSDID=__RCSID -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc In file included from /usr/include/stdio.h:44, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.h:57, from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc:21: /usr/include/sys/_types.h:71: declaration does not declare anything *** Error code 1 Which revision of /usr/include/sys/_types.h do you have? $ ident /usr/include/sys/_types.h /usr/include/sys/_types.h: $FreeBSD: src/sys/sys/_types.h,v 1.7 2002/08/25 19:26:31 mike Exp $ What is at, around, and near line 71 of /usr/include/sys/_types.h ? $ cat -n /usr/include/sys/_types.h | head -75 | tail -9 67 * character set plus one extra value (WEOF), and must be at least 16 bits. 68 */ 69 typedef int __ct_rune_t; 70 typedef __ct_rune_t __rune_t; 71 typedef __ct_rune_t __wchar_t; 72 typedef __ct_rune_t __wint_t; 73 74 /* 75 * mbstate_t is an opaque object to keep conversion state during multibyte To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
parallel ports
I've had a lot of problems--and so have a few others (very few) with the 4.6 kernels not recognizing parallel ports to the point they are not useable. simply cant use them to print. The kernel on boot spits out ppc0: cannot reserve range. I have installed 5.0-DP1 and it_does properly recognize the parallel ports. HOWEVER if I cvsup the kernel source and recompile a new kernel (fer instance, for sound card support) that capability goes away. Has anyone else seen this??? NOthing I have done with the 4.6- or 4.7 kernels has helped. Guess it's back to 5.0-DP1, if I want to print, eh? --karl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: i386 a.out binary users!
At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote: Peter Wemm wrote: You will need to either add: options COMPAT_AOUT to your kernel config when you next rebuild, or do a 'kldload aout' when you want to run an old a.out binary. Is this going to be turned on be default in the rc scripts, until such time as sysinstall is taught about asking the user the same way it asks the user about compatability packages or Linux emulation? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I cant get a kernel to compile without COMPAT_AOUT: (pro2)201}make linking kernel.debug imgact_gzip.o: In function `do_aout_hdr': ../../../kern/imgact_gzip.c:280: undefined reference to `aout_sysvec' *** Error code 1 Stop in /usr/src/sys/i386/compile/pro2. Works fine if I add options COMPAT_AOUT Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Notebook temperature issues and need help in disabling suspend/sleep mode
Hello all: I have a IBM ThinkPad 770Z notebook running the latest -current and I'm having a few issues. The first one is, is there a way to disable sleep/suspend when the lcd lid is closed since I only want the lcd display to be off but the machine still running normally. The second issue is the cpu fan doesn't seem to turn on even after I issued the following commands in /etc/rc.local as per one of the message threads on the list: /sbin/sysctl -w hw.acpi.thermal.tz0.active=1 /sbin/sysctl -w hw.acpi.thermal.tz1.active=1 /sbin/sysctl -w hw.acpi.thermal.tz2.active=1 /sbin/sysctl -w hw.acpi.thermal.tz3.active=1 /sbin/sysctl -w hw.acpi.thermal.tz4.active=1 /sbin/sysctl -w hw.acpi.thermal.tz5.active=1 /sbin/sysctl -w hw.acpi.thermal.tz6.active=1 This is the message on the console I get a few minutes before the system shuts off by itself without syncing the disk. Sep 7 17:09:42 exabyte kernel: acpi_tz0: WARNING - current temperature (97.8C) exceeds system limits This is what my sysctl hw.acpi output looks like: # sysctl hw.acpi hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3180 hw.acpi.thermal.tz0.active: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 3130 hw.acpi.thermal.tz1.active: 1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 3442 hw.acpi.thermal.tz1._ACx: 3402 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 3090 hw.acpi.thermal.tz2.active: 1 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: -1 hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 3372 hw.acpi.thermal.tz2._ACx: 3242 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz3.temperature: 3000 hw.acpi.thermal.tz3.active: 1 hw.acpi.thermal.tz3.thermal_flags: 0 hw.acpi.thermal.tz3._PSV: -1 hw.acpi.thermal.tz3._HOT: -1 hw.acpi.thermal.tz3._CRT: 3322 hw.acpi.thermal.tz3._ACx: 3272 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz4.temperature: 3050 hw.acpi.thermal.tz4.active: 1 hw.acpi.thermal.tz4.thermal_flags: 0 hw.acpi.thermal.tz4._PSV: -1 hw.acpi.thermal.tz4._HOT: -1 hw.acpi.thermal.tz4._CRT: 3392 hw.acpi.thermal.tz4._ACx: 3037 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz5.temperature: 3060 hw.acpi.thermal.tz5.active: 1 hw.acpi.thermal.tz5.thermal_flags: 0 hw.acpi.thermal.tz5._PSV: -1 hw.acpi.thermal.tz5._HOT: -1 hw.acpi.thermal.tz5._CRT: 3432 hw.acpi.thermal.tz5._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz6.temperature: 3000 hw.acpi.thermal.tz6.active: 1 hw.acpi.thermal.tz6.thermal_flags: 0 hw.acpi.thermal.tz6._PSV: -1 hw.acpi.thermal.tz6._HOT: -1 hw.acpi.thermal.tz6._CRT: 3432 hw.acpi.thermal.tz6._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 49 hw.acpi.battery.time: -1 hw.acpi.battery.state: 4 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 Any help would be greatly appreciated. Thanks in advance, KC To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: i386 a.out binary users!
On 7 Sep, Manfred Antar wrote:
At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote:
Peter Wemm wrote:
You will need to either add:
options COMPAT_AOUT
to your kernel config when you next rebuild, or do a 'kldload aout'
when you want to run an old a.out binary.
Is this going to be turned on be default in the rc scripts,
until such time as sysinstall is taught about asking the user
the same way it asks the user about compatability packages or
Linux emulation?
I cant get a kernel to compile without COMPAT_AOUT:
(pro2)201}make
linking kernel.debug
imgact_gzip.o: In function `do_aout_hdr':
../../../kern/imgact_gzip.c:280: undefined reference to `aout_sysvec'
*** Error code 1
Stop in /usr/src/sys/i386/compile/pro2.
Works fine if I add options COMPAT_AOUT
I didn't have that problem when I rebuilt the kernel and world four or
five hours ago, but there's no rc.conf knob to load the aout module, so
setiathome failed to start when I rebooted the system.
This knob should probably also be connected to the code in /etc/rc that
runs ${ldconfig} -aout
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/var/tmp/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Sat Sep 7 18:18:02 PDT 2002 -- Kernel build for GENERIC completed on Sat Sep 7 19:22:36 PDT 2002 -- Kernel build for LINT started on Sat Sep 7 19:22:36 PDT 2002 -- === LINT config: Error: device apm_saver is unknown config: Error: device cy is unknown config: Error: device cy does not take a count config: 3 errors WARNING: kernel contains GPL contaminated ext2fs filesystem FYI: static unit limits for vcoda are set: NVCODA=4 FYI: static unit limits for dgb are set: NDGB=1 FYI: static unit limits for card are set: NCARD=1 FYI: static unit limits for meteor are set: NMETEOR=1 *** Error code 1 Stop in /var/tmp/des/src. *** Error code 1 Stop in /var/tmp/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: i386 a.out binary users!
Manfred Antar wrote: At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote: Peter Wemm wrote: You will need to either add: options COMPAT_AOUT to your kernel config when you next rebuild, or do a 'kldload aout' when you want to run an old a.out binary. Is this going to be turned on be default in the rc scripts, until such time as sysinstall is taught about asking the user the same way it asks the user about compatability packages or Linux emulation? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I cant get a kernel to compile without COMPAT_AOUT: (pro2)201}make linking kernel.debug imgact_gzip.o: In function `do_aout_hdr': ../../../kern/imgact_gzip.c:280: undefined reference to `aout_sysvec' *** Error code 1 Stop in /usr/src/sys/i386/compile/pro2. Works fine if I add options COMPAT_AOUT options GZIP is support for running gzipped a.out executables. You probbly want to remove that instead. 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
make installworld cannot find files in /usr/bin
Hi, I did a cvsup from a few hours ago, and rebuilt the world. make buildworld worked fine. make installworld failed: === usr.sbin/ppp^M install -s -o root -g network -m 4554 ppp /usr/sbin m4 /usr/src/usr.sbin/ppp/ppp.8.m4 ppp.8 m4: not found I also had similar problems in /usr/src/share/termcap, because the Makefile there could not find /usr/bin/cap_mkdb and /usr/bin/ex. I worked around the problem by replacing references to m4, cap_mkdb, and ex in /usr/src/usr.sbin/ppp/Makefile and /usr/src/share/termcap/Makefile with fully qualified path names. Any ideas what could cause this? My environment has /usr/bin in its PATH. Also, if I manually cd to either of those directories and do: make install, then it finds the programs in /usr/bin with no problem. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Clock runs too fast
Hi, I have been having this problem with -current for the past 2 weeks now (I am new to -current and just started using it 2 weeks ago). I just did a cvsup and rebuilt the kernel and rebuilt the world. My clock seems to be running too fast, and I keep resetting it with ntpdate. I looked at this FAQ entry for hints, Why is the clock on my laptop keep incorrect time? http://www.unixguide.net/freebsd/faq/05.26.shtml My default sysctl value for kern.timecounter hardware is: kern.timecounter.hardware: ACPI-safe The Timecounters available on my system are: dmesg | grep Timecounter Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 400910436 Hz Timecounter ACPI-safe frequency 3579545 Hz Timecounters tick every 10.000 msec I reset my timecounter: sysctl kern.timecounter.hardware=i8254 Now the clock seems to run at a more reasonable rate. Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). How can I default to i8254 as my default timer? Is there something I should put in device.hints? -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: i386 a.out binary users!
At 07:27 PM 9/7/2002 -0700, Peter Wemm wrote: Manfred Antar wrote: At 12:23 AM 9/7/2002 -0700, Terry Lambert wrote: Peter Wemm wrote: You will need to either add: options COMPAT_AOUT to your kernel config when you next rebuild, or do a 'kldload aout' when you want to run an old a.out binary. Is this going to be turned on be default in the rc scripts, until such time as sysinstall is taught about asking the user the same way it asks the user about compatability packages or Linux emulation? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I cant get a kernel to compile without COMPAT_AOUT: (pro2)201}make linking kernel.debug imgact_gzip.o: In function `do_aout_hdr': ../../../kern/imgact_gzip.c:280: undefined reference to `aout_sysvec' *** Error code 1 Stop in /usr/src/sys/i386/compile/pro2. Works fine if I add options COMPAT_AOUT options GZIP is support for running gzipped a.out executables. You probbly want to remove that instead. Cheers, -Peter I thought it was for gzipped kernels which I use sometimes, So I left it in. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[PATCH] C++ fix for flex
Hi, As I am fixing some of the C++ ports for GCC 3.2, I found a problem with lex. The following patch is required for lex to generate code which can compile with GCC 3.2. It applies to /usr/src/usr.bin/lex --- flex.skl.orig Sat Sep 7 23:44:38 2002 +++ flex.sklSat Sep 7 23:45:06 2002 @@ -26,7 +26,8 @@ #include stdlib.h %+ -class istream; +#include iosfwd +using namespace std; %* #include unistd.h For Standard C++, you cannot forward declare istream as: class istream; because in Standard C++, istream is a typedef for a template: typedef basic_istreamchar istream; The correct fix is to include iosfwd. Under gcc 2.95, iosfwd forward declares istream as class istream; and under gcc 3.2, iosfwd forward declares istream as the typedef. The using namespace std; is required because in gcc 3.2, istream is in the std namespace. In gcc 2.95, this line will be benign. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC 3.2 patch
Quoting Alexander Kabaev [EMAIL PROTECTED]: | Hi everyone, | | I've collected a number of patches for several problems with | GCC 3.2 compiler which have been brought to my attention so far. | While I am waiting for these patches or other suitable fixes to be | incorporated into FSF CVS repository, I decided to make a patch | file available at http://people.freebsd.org/~kan/gcc-all.diff. | | People having problems compiling their problems with the new | system compiler are encouraged to give this patch a try and | let me know if their problem is fixed ot not. | | -- Alexander Kabaev | | To Unsubscribe: send mail to [EMAIL PROTECTED] | with unsubscribe freebsd-ports in the body of the message -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GCC 3.2 patch
Quoting Alexander Kabaev [EMAIL PROTECTED]: | Hi everyone, | | I've collected a number of patches for several problems with | GCC 3.2 compiler which have been brought to my attention so far. | While I am waiting for these patches or other suitable fixes to be | incorporated into FSF CVS repository, I decided to make a patch | file available at http://people.freebsd.org/~kan/gcc-all.diff. | | People having problems compiling their problems with the new | system compiler are encouraged to give this patch a try and | let me know if their problem is fixed ot not. | | -- Alexander, It did fix my problem. I did a cvsup and buildworld this morning over yesterday afternoon's application and build. It didn't even dawn on me until your email. I reapplied the patch and now it is fine. Thanks. I'll do more testing tomorrow but I'm sure it will solve some of my problems with port rebuilding. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ÔÈËÜÌ Ãîðåö ñ ÌàÊëàóäîì èìååò ðåàëüíóþ îñíîâó!!!!
Òåïåðü ýòî òû ìîæåøü çíàòü!!! Êàê âñåãäà ÷åëîâåê äóìàåò ,÷òî ÷óäåñà íå äëÿ íåãî.!? Ìîÿ èñòîðèÿ è ìîÿ æèçíü òåïåðü îòêðûòà äëÿ òåáÿ: http://multimail.info/people/novikov ×òî æ,óäèâèñü, íå ìíå,à òîìó,÷òî ýòî ìîæåøü áûòü è ÒÛ! Äà, òû ìîæåøü æèòü òàê äîëãî è çäîðîâûì,÷òî ñàì åùå íå çíàåøü! Ìíå ñåé÷àñ 73 ãîäà, à íà ñàìîì äåëå íå äàøü è 45! (ñì. ìîè ôîòî) ß ðàññêàæó êàê ñäåëàòü ñåáÿ ìîëîäûì ñ ëþáîãî âîçðàñòà, äàæå åñëè òû óæå ãîòîâèøüñÿ ê ñàìîìó ïëîõîìó -ê ñìåðòè. Ïðèâåòñòâóþ òåáÿ ìîé áóäóùèé äðóã. Ñåðãåé Íîâèêîâ. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Another compiler bug?
World-testing some changes to libc, I had g++ bomb out with the following assertion: In file included from /usr/obj/usr/src/i386/usr/include/g++/locale:46, from /usr/obj/usr/src/i386/usr/include/g++/bits/ostream.tcc:37, from /usr/obj/usr/src/i386/usr/include/g++/ostream:275, from /usr/src/contrib/libstdc++/src/ios.cc:36: /usr/obj/usr/src/i386/usr/include/g++/bits/locale_facets.h: In instantiation of `std::__timepunctwchar_t': /usr/obj/usr/src/i386/usr/include/g++/bits/locale_facets.tcc:2191: instantiated from here /usr/obj/usr/src/i386/usr/include/g++/bits/locale_facets.h:1057: Internal compiler error in tsubst_decl, at cp/pt.c:5774 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 I can provide the current-relative patches if anyone feels interested in investigating further (kan?). Applying kan's gcc-all.patch seems makes it better, although looking at the patch and the error message I don't understand why it would have any effect. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libmd bug on -CURRENT
If memory serves me right, Bruce Evans wrote: On Fri, 6 Sep 2002, Bruce A. Mah wrote: If memory serves me right, Poul-Henning Kamp wrote: Good catch. I'm surprised the compiler doesn't whine. Thanks, and me too. Warnings are mostly turned off for not unimportant places like libraries since these places are too poorly written to compile without warnings. Apparently. PS. Actually I'm surprised that nobody caught the problem in the past five months...this bug prevented release builds from 5-CURRENT hosts. Maybe I'm the only person crazy enough to try this. :-) This bug was caught in PR 42384. The fix in the PR is not so good. I suppose I didn't look hard enough when I scanned through the PR database. I'll deal with the PR. libmd is also broken for some cases involving pipes. IIRC, this is caused by the bogus st_size checks in the same function. st_size is only valid for regular files. It's puzzling that the call to lseek(2) doesn't always return an error in these cases as well (as the manpage seems to imply). Yet, one can do md5(1) on a pipe: tomcat:bmah% cat /etc/motd | md5 9caae6eae6f9c2dfea77d6a5fae2e93c tomcat:bmah% md5 /etc/motd MD5 (/etc/motd) = 9caae6eae6f9c2dfea77d6a5fae2e93c The loop in the function fails to to terminate if read() returns 0, which can probably happen if the file shrinks underneath us. Maybe add a check after the read(2), so that if it returns zero, we set n = 0? It's not clear to me what result should be returned in the case of trying to compute a checksum on a file that shrinks in the middle of the computation. Thanks, Bruce. msg42775/pgp0.pgp Description: PGP signature
