Re: Errors compiling kernel...
It seems Will Andrews wrote: On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote: I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and I'm getting these errors compiling the kernel: cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c ../../dev/ata/atapi-all.c: In function `atapi_attach': ../../dev/ata/atapi-all.c:96: syntax error before `}' *** Error code 1 Soren Schmidt (sos) made some recent commits to the ATA driver. Perhaps these problems are the result. Yup, braino on my part, fixed now. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
This is getting ridiculous..
/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o): In function `choose_temp_base': choose-temp.c(.text+0x218): warning: mktemp() possibly used unsafely; consider using mkstemp() /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In function `_gettemp': mktemp.c(.text+0x3f0): undefined reference to `_open' mktemp.c(.text+0x3f4): undefined reference to `_open' *** Error code 1 1 error This is from a freshly checked-out tree on beast, with no local mods outside of secure/. I've verified twice it's up-to-date with CVS.. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of ATAisms...
It seems Alex Zepeda wrote: OK, I got my junkbox back into commission today, I just need to get it update into -current, then I'll take a stab at it... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: This is getting ridiculous..
On Fri, Jan 28, 2000 at 12:05:21AM -0800, Kris Kennaway wrote: /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o): In function `choose_temp_base': choose-temp.c(.text+0x218): warning: mktemp() possibly used unsafely; consider using mkstemp() /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In function `_gettemp': mktemp.c(.text+0x3f0): undefined reference to `_open' mktemp.c(.text+0x3f4): undefined reference to `_open' *** Error code 1 1 error This is from a freshly checked-out tree on beast, with no local mods outside of secure/. I've verified twice it's up-to-date with CVS.. I'm still trying to test this patch before committing. Jason Index: SYS.h === RCS file: /home/ncvs/src/lib/libc/alpha/SYS.h,v retrieving revision 1.9 diff -u -r1.9 SYS.h --- SYS.h 2000/01/27 23:06:02 1.9 +++ SYS.h 2000/01/28 08:15:20 @@ -104,7 +104,7 @@ #definePSYSCALL(name) \ PLEAF(name,0); /* XXX # of args? */\ - WEAK_ALIAS(__CONCAT(_thread_sys_,name), name); \ + WEAK_ALIAS(__CONCAT(_,name), name); \ CALLSYS_ERROR(name) #definePRSYSCALL(name) \ @@ -115,7 +115,7 @@ #definePPSEUDO(label,name) \ PLEAF(label,0);/* XXX # of args? */\ - WEAK_ALIAS(__CONCAT(_thread_sys_,name), name); \ + WEAK_ALIAS(__CONCAT(_,name), name); \ CALLSYS_ERROR(name);\ RET;\ PEND(label) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rsh broken?
with yesterdays kernel or rshd, something has changed. When using rsh from a friendly linux-mandrake box i get: rsh jfh00 ls poll: protocol failure in circuit setup from a friendly freebsd box i get: select: protocol failure in circuit setup -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current is still broken as of 2000/01/27
On Thu, 27 Jan 2000 18:35:33 PST, Jason Evans wrote: This is the same kind of breakage I caused when moving some definitions into unistd.h. I would call it bootstrapping breakage, but others who know the build system better claim it's avoidable. I think it _is_ avoidable. One way to avoid it is to try to make world and report the brekage to -committers, asking for help. This works best when you do it _before_ committing the change you're testing. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rsh broken?
with yesterdays kernel or rshd, something has changed. When using rsh from a friendly linux-mandrake box i get: rsh jfh00 ls poll: protocol failure in circuit setup from a friendly freebsd box i get: select: protocol failure in circuit setup As the change to src/lib/libc/net/getaddrinfo.c 1.4 - 1.5, there emerged a bug in realhostname_sa() in lib/libutil/realhostname.c. If your lib/libutil/realhostname.c's version is lower than 1.5, then please update it and try again. Else, I need to investigate it more Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: This is getting ridiculous..
/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In function `_gettemp': mktemp.c(.text+0x3f0): undefined reference to `_open' mktemp.c(.text+0x3f4): undefined reference to `_open' *** Error code 1 1 error Yes, I expected this error after seeing the libc chagnes. Unfortunetly, the setflags() barfage make it so I couldn't buildworld to test a change to the compiler before committing it. :-( -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Keyboard problem (was: Re: Problems installing FreeBSD 4.0 20000125-CURRENT)
Ok, guys.
This is another patch for the atkbd driver. I expect this one is
better than my previous one. Remove the previous patch and try this
one instead. Stress the keyboard (like hitting the Return key twice
when booting the system), and see if it works.
Thank you.
Kazu
I have on a number of occasions had my laptop boot with a
non-functional keyboard. Sometimes the keyboard is just locked; other
times it generates garbage. Never managed to isolate the
circumstances in which this happened (but it didn't happen with a
kernel from last September or there-abouts). Haven't had it happen on
a desktop or server yet.
I have seen this on numerious occasion, but have never tracked it down
to any one specific thing. All on desktop and servers, but thats
only because we don't do laptops.
I have not seen it in quite some time (about a month), so I am thinking
it has probably been unknowingly fixed someplace. I'll keep an eye
out for it.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
Index: atkbd.c
===
RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v
retrieving revision 1.22
diff -u -r1.22 atkbd.c
--- atkbd.c 2000/01/20 13:32:53 1.22
+++ atkbd.c 2000/01/28 02:11:50
@@ -1084,8 +1097,11 @@
return ENXIO;
}
+ /* temporarily block data transmission from the keyboard */
+ write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT);
+
/* flush any noise in the buffer */
- empty_both_buffers(kbdc, 10);
+ empty_both_buffers(kbdc, 100);
/* save the current keyboard controller command byte */
m = kbdc_get_device_mask(kbdc) ~KBD_KBD_CONTROL_BITS;
@@ -1133,8 +1148,11 @@
return EIO;
}
+ /* temporarily block data transmission from the keyboard */
+ write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT);
+
/* save the current controller command byte */
empty_both_buffers(kbdc, 200);
c = get_controller_command_byte(kbdc);
if (c == -1) {
/* CONTROLLER ERROR */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ColdFusion 4.5 RC3
I totally aggree. As soon as CF is ported to FreeBSD the bettter At 21:20 27/01/00 -0500, James Howard wrote: On Thu, 27 Jan 2000, Brian Hechinger wrote: yes. sorry about the confusion, i forgot to mention that. Allaire off-record said that they aren't happy with Linux and are seeking an alternative. i seem to be pushing them towards FreeBSD. but, keep in mind, this will be a huge shift in development for them, so if they ever do descide this, it still won't happen for a while. I was quite happy with Cold Fusion under NT. Significantly better than ASPs :) Anyway, I'd love to see a FreeBSD port, is there an email address where we can politely encourage them? Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thursday, 27th January 2000, "Rodney W. Grimes" wrote: On Thu, 27 Jan 2000 13:28:10 -0800, "Jordan K. Hubbard" [EMAIL PROTECTED] said: 3. On the first reboot after installing, the keyboard was in a funny state. I have seen this on numerious occasion, but have never tracked it down to any one specific thing. All on desktop and servers, but thats only because we don't do laptops. I have not seen it in quite some time (about a month), so I am thinking it has probably been unknowingly fixed someplace. I'll keep an eye out for it. I had this problem on several machines back around version 3.2. I assumed it was a problem between X11 and the keyboard driver. I added a 2 second delay before starting xdm and had no problems after that. I've not seen the problem without X11 being involved. I admit I just forgot about it after I got my workstation going. :-( Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rsh broken?
When using rsh from a friendly linux-mandrake box i get:
rsh jfh00 ls
poll: protocol failure in circuit setup
from a friendly freebsd box i get:
select: protocol failure in circuit setup
Woops bug was in rshd from the beginning. My test had a
leakage. It only happens on AF_INET socket, and I usually use
AF_INET6 socket on my environment so I didon't noticed it.
Please try following patch untill I actually commmit it.
Thanks for reporting it,
Yoshinobu Inoue
Index: rshd.c
===
RCS file: /home/ncvs/src/libexec/rshd/rshd.c,v
retrieving revision 1.28
diff -u -r1.28 rshd.c
--- rshd.c 2000/01/25 14:52:03 1.28
+++ rshd.c 2000/01/28 12:51:13
@@ -320,7 +320,7 @@
exit(1);
}
fromp-su_port = htons(port);
- if (connect(s, (struct sockaddr *)fromp, sizeof (*fromp)) 0) {
+ if (connect(s, (struct sockaddr *)fromp, fromp-su_len) 0) {
syslog(LOG_INFO, "connect second port %d: %m", port);
exit(1);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: NFS /usr/src and /usr/obj?
In message [EMAIL PROTECTED], Leif Neland writes: On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], [EMAIL PROTECTED] writes: I'm wondering how one can do a buildworld on a machine, and then NFS mount /usr/src and /usr/obj on a client machine and do an installworld of the freshly built sources? I've been looking in the archives without much success, and haven't figured it out by reading the makefiles yet. Can anyone shed some light on this? I've done it in the past, but not recently. Consider the alternative of mounting the destination on the compilehost and make install DESTDIR=/mnt A: What's the advantage? That your server mounts the clients, not the other way around (security etc) B: What do I mount? The root of the destination? All relevant filesystems of the destination, ie: /, /var, /usr -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipsec errors
On Thu, 27 Jan 2000 13:46:47 +0900, Yoshinobu Inoue wrote: I just added debug flag check instead of changing syslog level. Could you please try the following patch to usr.sbin/inetd/inetd.c ? I would expect the messages to be sent to stderr in debug mode. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
On Thu, 27 Jan 2000 18:53:51 -0800, Mike Smith [EMAIL PROTECTED] said: Since the hostname is simply a plain-text token for the IP address Wrong. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
... Starting an 'fsck' results in: cage:[/] # fsck /scratch ** /dev/da1s1g ** Last Mounted on /scratch ** Phase 1 - Check Blocks and Sizes PARTIALLY TRUNCATED INODE I=16 SALVAGE? [yn] ^C * FILE SYSTEM MARKED DIRTY * Next step is run the ``save'' fsck: fsck -n /scratch /someplacewithspace 21 Then take a look at the logfile and see just how many more errors it would have found had you let it procede... I interrupted the fsck-run as soon as I decided that it might be advisable to leave it in its hosed state just for the case that there is some illuminated filesystem-hacker who would like to take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it if you need it. I don't do it for fun. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Makefile.inc1 change
The following has survived a make buildworld at least once. It
optimizes buildworld a little by not building fortran as part of the
build tools.
This looks like a safe change to make, since we have no fortran in the
tree that needs to get built. It doesn't disable building of fortran
later in the build, just from building it potentially twice.
Comments?
Warner
Index: Makefile.inc1
===
RCS file: /home/imp/FreeBSD/CVS/src/Makefile.inc1,v
retrieving revision 1.133
diff -u -r1.133 Makefile.inc1
--- Makefile.inc1 2000/01/24 20:11:53 1.133
+++ Makefile.inc1 2000/01/28 09:21:39
@@ -503,10 +503,6 @@
_share=share/syscons/scrnmaps
.endif
-.if !defined(NO_FORTRAN)
-_fortran= gnu/usr.bin/cc/f771
-.endif
-
.if exists(${.CURDIR}/kerberosIV) exists(${.CURDIR}/crypto) \
!defined(NOCRYPT) defined(MAKE_KERBEROS4)
_libroken4= kerberosIV/lib/libroken
@@ -518,7 +514,7 @@
.endif
build-tools:
-.for _tool in bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \
+.for _tool in bin/sh ${_games} gnu/usr.bin/cc/cc_tools \
${_libroken4} ${_libroken5} lib/libncurses ${_share}
cd ${.CURDIR}/${_tool}; ${MAKE} build-tools
.endfor
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ata: panic with new sysctl variable
Hi, just noticed the new sysctl variable for ata. I just wanted to use the new way for disabling DMA on my disk (has some strange problems, even under windows). Previously I just commented out the ata_dmainit() lines in ata_disk.c, now I wanted to set it with sysctl: sysctl -w hw.atamodes="pio,dma,dma,dma" but this paniced my machine. I later discovered that there is no sanity check during setting the new modes: The machine in question didn't have a secondary IDE controller, but the variables were set without a range check. My solution was simple. Just use sysctl -w hw.atamodes="pio,dma" but I think, the ata driver should range check the settings. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata: panic with new sysctl variable
It seems D. Rock wrote: Hi, just noticed the new sysctl variable for ata. I just wanted to use the new way for disabling DMA on my disk (has some strange problems, even under windows). Previously I just commented out the ata_dmainit() lines in ata_disk.c, now I wanted to set it with sysctl: sysctl -w hw.atamodes="pio,dma,dma,dma" but this paniced my machine. I later discovered that there is no sanity check during setting the new modes: The machine in question didn't have a secondary IDE controller, but the variables were set without a range check. My solution was simple. Just use sysctl -w hw.atamodes="pio,dma" but I think, the ata driver should range check the settings. It does but not for the first two devices as the are kindof magic in some sense. I'll commit the fix asap.. -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: very silent, but heavy filesystem-crash
:Hi there, : : I reported a former heavy filesystem crash recently; have a look : at: : :http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/2123.freebsd-current : : I got it again. : Meanwhile my system got updated to : FreeBSD abc.xyz.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 11:17:16 CET 2000 : : The system is complete soft-updates free. : : This time I had no jailed processes running; the machine was idle : most of the time during the last few days and was rebooted (cleanly), : yesterday. : : The (now totally hosed) file-system was mounted thru the following : fstab-entry: : :/dev/da1s1g /scratch ufs rw 2 2 :Bye, :Andreas :Andreas Braukmann - private site - cat /etc/fstab disklabel da1s1 (so it prints out the label) There's a good chance you overlapped a partition. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
On Fri, Jan 28, 2000 at 09:33:32AM -0700, Warner Losh wrote: This looks like a safe change to make, since we have no fortran in the tree that needs to get built. It doesn't disable building of fortran later in the build, just from building it potentially twice. Comments? I like it. If it passes a clean and -DNOCLEAN buildworld, commit that baby! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] "David O'Brien" writes: : I like it. If it passes a clean and -DNOCLEAN buildworld, commit that : baby! OK. It passes a clean buildworld + installworld. I'll crank up the -DNOCLEAN right now. Looks like the savings aren't huge. Like 3 minutes out of 140 on my fast machine. More on my slow machine. Still 2% increase in buildworld times for a 5 line hack isn't that bad, no? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
-On [2128 19:30], John Baldwin ([EMAIL PROTECTED]) wrote: === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. In the meantime, should you encounter a broken make world with this use the following WORKAROUND: cd /usr/src/usr.bin/xinstall make make install and resume the make world. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: More world breakage
On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: === bin/pwd install -c -s -o root -g wheel -m 555 pwd /bin install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 This is the second or third make world to bomb on me with the same error. I ensured sources and such were clean. I think David O`Brien saw the same breakage. This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. The long version is this: Problem: It would seem from Asmodai's breakage that installworld assumes that it is ok to use the existing binaries on the system in /bin /usr/bin, etc. to install the new ones. However, if you have a rare case like this where the old and new libs/progs are incompatible, then there is a window between the installation of the different parts where you can get screwed. For example, here the new libc gets installed, which doesn't have the 'strings_to_flags' call. The old install program (not yet replaced) tries to call the 'string_to_flags' function which was present in the old libc but which isn't around anymore. Boom! Solution: We need statically built install tools just like we have build tools. I think we should use the newer versions (i.e. static versions of the ones we just built under /usr/obj during buildworld that are linked against the new libraries), rather than doing some fancy footwork to make the existing binaries work. We already do this with the build tools. By using the newer binaries we only have to maintain one interface in our Makefiles to the install tools: whatever their current interface is in /usr/src. Comments, suggestions? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Parallel port back
My parallel port is back. Switching the it from 3BC to 378 made the probe recognize it again. Apparently the new code doesn't like the 3BC address as much as the old code.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: === bin/pwd install -c -s -o root -g wheel -m 555 pwd /bin install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 [snip] This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. The long version is this: [snip] It would seem from Asmodai's breakage that installworld assumes that it is ok to use the existing binaries on the system in /bin /usr/bin, etc. [snip] We need statically built install tools just like we have build tools. [snip] Comments, suggestions? [snip] I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. FYI, marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
On 28-Jan-00 Marcel Moolenaar wrote: On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: === bin/pwd install -c -s -o root -g wheel -m 555 pwd /bin install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 === bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 [snip] This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. The long version is this: [snip] It would seem from Asmodai's breakage that installworld assumes that it is ok to use the existing binaries on the system in /bin /usr/bin, etc. [snip] We need statically built install tools just like we have build tools. [snip] Comments, suggestions? [snip] I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. This isn't related to the kernel though, it is a dependency within the world between libraries and binaries. Do you have those patches somewhere where I can look at them. I want to start testing them, because it _may_ (I'm only saying "may" right now) be better to fix this before 4.0 so that we don't have 4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 being only for early adopters) and then running into this and flooding -questions. I'd like to prevent a FAQ rather than create one, if you know what I mean. FYI, marcel -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
Marcel Moolenaar wrote: I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. The buildkernel target seems to be broke. The following sequence was followed (starting at 0900 PST ): %cvsup supfile.current %cd /usr/src %make -j 4 buildworld %setenv KERNEL SGK %make buildkernel -- Steve cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/net/if_ethersubr.c /usr/src/sys/net/if_ethersubr.c: In function `ether_output': /usr/src/sys/net/if_ethersubr.c:215: `ETHER_HDR_LEN' undeclared (first use in this function) /usr/src/sys/net/if_ethersubr.c:215: (Each undeclared identifier is reported only once [20 more warnings/errors deleted]. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
sgk wrote: Marcel Moolenaar wrote: I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. The buildkernel target seems to be broke. The following sequence was followed (starting at 0900 PST ): %cvsup supfile.current %cd /usr/src %make -j 4 buildworld %setenv KERNEL SGK %make buildkernel AARGH! Please, ignore. I some how removed "options INET" from my configuration files. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
-On [2128 20:00], Warner Losh ([EMAIL PROTECTED]) wrote: In message [EMAIL PROTECTED] "David O'Brien" writes: : I like it. If it passes a clean and -DNOCLEAN buildworld, commit that : baby! OK. It passes a clean buildworld + installworld. I'll crank up the -DNOCLEAN right now. Looks like the savings aren't huge. Like 3 minutes out of 140 on my fast machine. More on my slow machine. Still 2% increase in buildworld times for a 5 line hack isn't that bad, no? All the bits help. =) And anyways, as you said, compiling it twice seems a bit unnecessary. Feel free to commit when you're sure. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai How the gods kill... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] Jeroen Ruigrok/Asmodai writes: : All the bits help. =) : : And anyways, as you said, compiling it twice seems a bit unnecessary. : : Feel free to commit when you're sure. I'm sure. I did a make buildworld make installworld. I then did a make buildworld -DNOCLEAN. No ill effects from this change were detected. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. This isn't related to the kernel though, it is a dependency within the world between libraries and binaries. It's also related to the kernel, where installworld is installing and subsequently running binaries that won't work with the current kernel. The same applies to installing shared binaries and running them without the proper libraries. Do you have those patches somewhere where I can look at them. I want to start testing them, because it _may_ (I'm only saying "may" right now) be better to fix this before 4.0 so that we don't have 4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 being only for early adopters) and then running into this and flooding -questions. I'd like to prevent a FAQ rather than create one, if you know what I mean. I don't think we should change yet another thing before a release. The problem shouldn't have been created this close to a release in the first place. We have to stop somewhere, and I think we should stop "fixing" right here, right now unless there's a *really* good reason not to (IMO of course). BTW: I've posted the patches before on -committers IIRC... marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ColdFusion 4.5 RC3
Are there differences in the Linux emulation from -stable - -current? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Hechinger Sent: Thursday, January 27, 2000 5:34 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: ColdFusion 4.5 RC3 I can consistantly get ColdFusion 4.5 RC3 installed on FreeBSD-current. It will not work on -stable (i didn't really mess with it too much however) i haven't gotten the Apache module to work yet (but i haven't even looked at it, so give me time) instructions are at http://users.tmok.com/~wonko/cf -wonko 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
new C++ compiler changes
I just put a new -current on my test machine, and watched a bunch of stuff fall over and die due to the new C++ implementation. Is it possible to bump the revision of libstdc++ (and perhaps others) so that existing programs can continue to function? I fear I will be tracking down occasional broken C++ programs for days now. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More world breakage
On 28-Jan-00 Marcel Moolenaar wrote: It's also related to the kernel, where installworld is installing and subsequently running binaries that won't work with the current kernel. The same applies to installing shared binaries and running them without the proper libraries. Ok, I'll buy that. :) Do you have those patches somewhere where I can look at them. I want to start testing them, because it _may_ (I'm only saying "may" right now) be better to fix this before 4.0 so that we don't have 4 million users using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 being only for early adopters) and then running into this and flooding -questions. I'd like to prevent a FAQ rather than create one, if you know what I mean. I don't think we should change yet another thing before a release. The problem shouldn't have been created this close to a release in the first place. We have to stop somewhere, and I think we should stop "fixing" right here, right now unless there's a *really* good reason not to (IMO of course). You're right. I guess the proper solution is to just back these changes out until after 4.0 when you can finish fixing up install side of 'world'. I just got ahead of myself a little. BTW: I've posted the patches before on -committers IIRC... Probably, another case of too much energy and not quite enough careful thought on my part. marcel -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: Is it possible to bump the revision of libstdc++ (and perhaps others) so that existing programs can continue to function? Nope. This is -CURRENT and this type of thing happens. And with a RELEASE about to happen, I don't want people continually asking for these old libs. Right now I can easily diagnose the problem and determine which libs are -fno-vtable-thunks and which are -fvtable-thunks. I fear I will be tracking down occasional broken C++ programs for days now. I'd rather people flushed out the old libs now, than have them haunt us in weird ways for months. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
On Fri, 28 Jan 2000, Warner Losh wrote: The following has survived a make buildworld at least once. It optimizes buildworld a little by not building fortran as part of the build tools. This breaks bootetrapping of fortran. Fortran is not built as a build- tool. Only a tool to build fortran is built. This tool is like the internal tools for sh and libcurses, etc. It must be built in the host environment, since the version built in the target environment may not run. Tests of tools need to test building from an old and foreign environment, e.g., 3.3 for alpha. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] Bruce Evans writes: : This breaks bootetrapping of fortran. Fortran is not built as a build- : tool. Only a tool to build fortran is built. This tool is like the : internal tools for sh and libcurses, etc. It must be built in the host : environment, since the version built in the target environment may not : run. : : Tests of tools need to test building from an old and foreign environment, : e.g., 3.3 for alpha. So I should back this out? I didn't do a 3.3 buildworld. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: More world breakage
On Fri, 28 Jan 2000, John Baldwin wrote: ... Solution: We need statically built install tools just like we have build tools. I think we should use the newer versions (i.e. static versions of the ones we just built under /usr/obj during buildworld that are linked against the new libraries), rather than doing some fancy footwork to Using the newer version would be even more broken, since they may be for another arch, or may just use new syscalls that don't exist in the host kernel. make the existing binaries work. We already do this with the build tools. By using the newer binaries we only have to maintain one interface in our Makefiles to the install tools: whatever their current interface is in /usr/src. The build-tools are carefully built so that work in the host environment. Essentially the same thing needs to be done for installation tools. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
[I said about ntpd usage of sched_* functions:] We should make them standard IMO. According to John Polstra: I agree. BTW, as the sched_* POSIX functions are now standard in GENERIC, I've decided along with the upgrade to ntpd 4.0.99b to re-enable them. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
On Fri, 28 Jan 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Bruce Evans writes: : This breaks bootetrapping of fortran. Fortran is not built as a build- : tool. Only a tool to build fortran is built. This tool is like the : internal tools for sh and libcurses, etc. It must be built in the host : environment, since the version built in the target environment may not : run. : : Tests of tools need to test building from an old and foreign environment, : e.g., 3.3 for alpha. So I should back this out? I didn't do a 3.3 buildworld. Of course. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: Is it possible to bump the revision of libstdc++ (and perhaps others) so that existing programs can continue to function? Nope. This is -CURRENT and this type of thing happens. And with a RELEASE about to happen, I don't want people continually asking for these old libs. Well, OK, I can deal with this myself. I'm just concerned about the folks who will eventually upgrade from 3.4 to 4.0, and have their C++ programs stop working. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Makefile.inc1 change
In message [EMAIL PROTECTED] Bruce Evans writes: : So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I'm doing a 3.3 buildworld right now on a virgin 3.3R system. I'll let you know what happens with that. If it is a problem at all, then I'll back it out (since others have asked me privately to run the test and not back it out unless there are problems). The program that it was building was definitely the first pass of the fortran compiler. What in the tree needs this in order to build, even on the alpha? I could find only one .f file in the entire tree and it looked like a test file, which didn't seem to be referenced in the makefile at all. What's the alpha problem? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems installing FreeBSD 4.0 20000125-CURRENT
Kazutaka YOKOTA wrote: I have had reports on similar lockup in both 4.0-CURRENT and 3.X. I personally have not been able to reproduce it, but now my new sand box machine exhibits this problem occasionally. The I/O access to the AT keyboard by the atkbd driver have not changed much for the last couple of years, despite massive source tree reorganization. And yes, problem reports started to pop-up since sometime around the last summer. I have not been able to track down the cause of the problem, but am suspecting possibility of the clock/timer problem. It happens with me from time to time. It is NOT related to kernel, since it happens between boot0 and boot2. It will happen when I'm typing something during boot, so it's probably some sort of race. Symptons include keys having weird mappings, and some keys not mapping to anything at all, after boot. At boot2/loader, no keypress is recognized at all. Very rare. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "2 b or not to b" meaning varies depending on whether one uses the 79 or the 83 standard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
