Re: RELENG_6 build failures
On Tue, Aug 25, 2009 at 09:42:03PM +, Bjoern A. Zeeb wrote: Hi, I was trying to run a make universe on RELENG_6 and found: 1) alpha doesn't build 2) powerpc LINT fails with: config: Error: device zs is unknown 3) sparc64 LINT fails with: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/tmp/usr/include -I/obj/sparc64/RELENG_6.svn/sys/LINT /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c:418:21: ukbdmap.h: No such file or directory At least (3) should be a supported platform but given that universe builds the other two as well I would assume they are as well. amd64, i386, pc98, ia64 were ok, the GENERIC kernels seems to be fine for powerpc and sparc64. alpha as said seems dead. I have no idea why we never saw the errors flying by, so I don't want to rule out a local problem. In case anyone could confirm these findings (or fix them should they exist) that would be great. I had run: make -j8 universe __MAKE_CONF=/dev/null AFAICT (3) isn't platform-specific but doesn't manifest with every build. The fix is to MFC rev. 1.57 of sys/dev/usb/ukbd.c (I don't seem to be able to access sys/legacy/dev/usb/ukbd.c for getting the SVN revision and sys/dev/usb/input/ukbd.c apparently wasn't copied from the old one within SVN). Marius ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_6 build failures
On Wed, 26 Aug 2009, Marius Strobl wrote: On Tue, Aug 25, 2009 at 09:42:03PM +, Bjoern A. Zeeb wrote: Hi, I was trying to run a make universe on RELENG_6 and found: 1) alpha doesn't build 2) powerpc LINT fails with: config: Error: device zs is unknown 3) sparc64 LINT fails with: mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/tmp/usr/include -I/obj/sparc64/RELENG_6.svn/sys/LINT /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c /RELENG_6.svn/sys/modules/ukbd/../../dev/usb/ukbd.c:418:21: ukbdmap.h: No such file or directory At least (3) should be a supported platform but given that universe builds the other two as well I would assume they are as well. amd64, i386, pc98, ia64 were ok, the GENERIC kernels seems to be fine for powerpc and sparc64. alpha as said seems dead. I have no idea why we never saw the errors flying by, so I don't want to rule out a local problem. In case anyone could confirm these findings (or fix them should they exist) that would be great. I had run: make -j8 universe __MAKE_CONF=/dev/null AFAICT (3) isn't platform-specific but doesn't manifest with every build. The fix is to MFC rev. 1.57 of sys/dev/usb/ukbd.c (I don't seem to be able to access sys/legacy/dev/usb/ukbd.c for getting the SVN revision and sys/dev/usb/input/ukbd.c apparently wasn't copied from the old one within SVN). Ah, good to know. You need the last known revision the file had been there still: http://svn.freebsd.org/viewvc/base/head/sys/legacy/dev/usb/ukbd.c?view=logpathrev=192900 so you probably mean: http://svn.freebsd.org/viewvc/base?view=revisionrevision=162959 /bz -- Bjoern A. Zeeb What was I talking about and who are you again? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
On Wednesday 26 August 2009 05:34:11 Nenhum_de_Nos wrote: On Tue, 25 Aug 2009 07:28:48 -0700 Doug Barton do...@freebsd.org wrote: Nenhum_de_Nos wrote: that's just what I was looking for. after the library bumps that happened after BETA2, I'd like to rebuild all :) There is an extensive writeup in the EXAMPLES section of the man page on how to rebuild all of your ports. I don't actually recommend that people use '-af' for that, although in theory it should work. yeah, I got bad luck. kBuild won't build in my machine. I had this before and just reinstalling solved. even pkg_delete -a didn't helped :( For some reason portmaster will not build kBuild or ports building with kBuild (such as virtulabox). However a manual make install clean works fine for me. I guess it's a bug in portmaster. Best Regards Troels Kofoed Jacobsen thanks, matheus Good luck, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-BETA3 gets wrong number of sectors per track on install
Just testing the new BETA3 of 8.0 - I did a vanilla install using auto layout and no odd options on my first hard drive. The installer sees the disc as having 63 sectors per track. Upon booting the installed OS, however, the device driver reports 32 sectors per track, as below: da0 at ciss0 bus 0 target 0 lun 0 da0: COMPAQ RAID 0 VOLUME OK Fixed Direct Access SCSI-5 device da0: 135.168MB/s transfers da0: Command Queueing enabled So I then get the following warning: GEOM: da0: partition 1 does not start on a track boundary. GEOM: da0: partition 1 does not end on a track boundary. GEOM: da0s1: geometry does not match label (255h,63s != 255h,32s). The relevent bits regarding the controller are: ciss0: HP Smart Array P400 port 0xb800-0xb8ff mem 0xf7d0-0xf7df,0xf7cff000-0xf7cf irq 18 at device 0.0 on pci1 ciss0: PERFORMANT Transport ciss0: Using MSIX interrupt ciss0: [ITHREAD] Not a major problem, more of an irritation, but I am puzzled as to why the installer is seeing the wrong values. -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
kbdcontrol: map Backspace key to '\' fails
On FreeBSD 7.2-STABLE it seems to be impossible to map the Backspace key to '\' and '|'. Here's what I did: Change /usr/share/syscons/keymaps/us.unix.kbd: --- us.unix.kbd-2009-07-17 16:43:35.0 -0700 +++ us.unix.kbd 2009-08-05 08:08:26.0 -0700 @@ -17,7 +17,8 @@ 011 '0'')'nopnop'0'')'nopnop O 012 '-''_'us us '-''_'us us O 013 '=''+'nopnop'=''+'nopnop O - 014 deldelbs bs deldelbs bs O +# 014 deldelbs bs deldelbs bs O + 014 '\''|'fs fs '\''|'fs fs O 015 ht btab nopnopht btab nopnop O 016 'q''Q'dc1dc1'q''Q'dc1dc1 C 017 'w''W'etbetb'w''W'etbetb C @@ -46,7 +47,8 @@ 040 '''''nopnop'''''nopnop O 041 escescescescescescdebug esc O 042 lshift lshift lshift lshift lshift lshift lshift lshift O - 043 '\''|'fs fs '\''|'fs fs O +# 043 '\''|'fs fs '\''|'fs fs O + 043 bs bs deldeldeldelbs bs O 044 'z''Z'subsub'z''Z'subsub C 045 'x''X'cancan'x''X'cancan C 046 'c''C'etxetx'c''C'etxetx C and run: kbdcontrol -k /dev/console -l /usr/share/syscons/keymaps/us.unix.kbd AFAICT this worked under 7.1 release. If I try a different character than backslash, e.g., 014 '0''|'fs fs '\''|'fs fs O it works. Is this a regression or user error? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
Troels Kofoed Jacobsen wrote: For some reason portmaster will not build kBuild or ports building with kBuild (such as virtulabox). However a manual make install clean works fine for me. I guess it's a bug in portmaster. Don't guess. :) The bug is in kBuild. Portmaster makes heavy use of environment variables, some of which can grow quite large. Something in kBuild overflows at some point in the build process due to the large environment space. IIRC someone volunteered to report this to the kBuild folks, but I never heard back from them about it. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
Skip Ford wrote: Doug Barton wrote: Yes, unfortunately it's not omniscient. :) Well, to be honest, it wouldn't need to be. It would just need a flag to know when nobody is present from whom to request input, and then take the default action. That's never going to happen. The default choice is not going to be the right one for some percentage of users. But, if all input is requested during config, then that's pointless. Yes, that's the goal. Second, without knowing what command line you used I couldn't tell you for sure what happened of course, but assuming you used some combination of '-af' what you saw was expected behavior. There is a conflict (I think a fairly obvious one) between the -f option and +IGNOREME. Since different users would have different ideas of how to resolve that conflict, portmaster takes the safe path and asks you. Well, it wasn't immediately obvious to me that someone would ever want to mark a port ignore and then want to upgrade it. So, it just seemed like a silly question to me (and still does to be honest, unless that's the behavior of portupgrade you're trying to match.) I honestly don't know what portupgrade does in that situation. There are at least 2 classes of users that I am trying to protect in this case: 1. Users who believe that -f should override +IGNOREME 2. Users who create an +IGNOREME file for some reason, then forget it's there. One of the problems with writing a tool like portmaster is that a lot of users have very strong ideas about how it should work, and very clear reasons for why they think that their way of looking at it is the right way. :) Unfortunately, there is usually an equal number of users on the other side who feel just as strongly. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
Date: Wed, 26 Aug 2009 12:59:19 -0700 From: Doug Barton do...@freebsd.org Sender: owner-freebsd-sta...@freebsd.org Skip Ford wrote: Doug Barton wrote: Yes, unfortunately it's not omniscient. :) Well, to be honest, it wouldn't need to be. It would just need a flag to know when nobody is present from whom to request input, and then take the default action. That's never going to happen. The default choice is not going to be the right one for some percentage of users. But, if all input is requested during config, then that's pointless. Yes, that's the goal. Second, without knowing what command line you used I couldn't tell you for sure what happened of course, but assuming you used some combination of '-af' what you saw was expected behavior. There is a conflict (I think a fairly obvious one) between the -f option and +IGNOREME. Since different users would have different ideas of how to resolve that conflict, portmaster takes the safe path and asks you. Well, it wasn't immediately obvious to me that someone would ever want to mark a port ignore and then want to upgrade it. So, it just seemed like a silly question to me (and still does to be honest, unless that's the behavior of portupgrade you're trying to match.) I honestly don't know what portupgrade does in that situation. There are at least 2 classes of users that I am trying to protect in this case: 1. Users who believe that -f should override +IGNOREME 2. Users who create an +IGNOREME file for some reason, then forget it's there. portupgrade does the same thing except that you hold them instead of ignoring them. I believe that this is the correct way. I have ports (e.g. openoffice.org) that take a VERY long time to build or that are run in production out of a crontab (rancid). I don't want to inadvertently update these with the '-a' option. (Especially th latter case.) When I really, really want to do them, I use '-f'. I think of '-f' as YES, I REALLY, REALLY, REALLY want to update this port now and I expect you to believe me. One of the problems with writing a tool like portmaster is that a lot of users have very strong ideas about how it should work, and very clear reasons for why they think that their way of looking at it is the right way. :) Unfortunately, there is usually an equal number of users on the other side who feel just as strongly. Yep, You can never design a tool more complex than a rock that will please everyone. Wait, that rock is too (soft | small | large | rounded | sharp | etc) for me. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: portmaster not ask for port deletion
On Wed, August 26, 2009 16:51, Doug Barton wrote: Troels Kofoed Jacobsen wrote: For some reason portmaster will not build kBuild or ports building with kBuild (such as virtulabox). However a manual make install clean works fine for me. I guess it's a bug in portmaster. Don't guess. :) The bug is in kBuild. Portmaster makes heavy use of environment variables, some of which can grow quite large. Something in kBuild overflows at some point in the build process due to the large environment space. IIRC someone volunteered to report this to the kBuild folks, but I never heard back from them about it. hail, a make install clean did the job really. got curious about what is this. cause firing portmaster /path/to/port is realy great :) matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
