Re: php5-pgsql and postgresql 9.1.1
On Thu, Nov 10, 2011 at 2:30 AM, Robert Simmons rsimmo...@gmail.com wrote: I'm trying to get the php5-pgsql module to work with postgresql 9.1.1, the current version in ports. It seems that when I install php5-pgsql from ports it depends on postgresql 8.4.9. I don't see anything in the Makefile that allows me to change this. How do I get the php5-pgsql port to see that I have postgres 9.1.1 installed? I figured it out. You just need to have the database installed before the php module. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com wrote: My assumption still is: Not _every_ keyboard manufacturer does code the layout into the USB identification. If you tell me I'm wrong with this assumption, I'll be happy. :-) Folks are supposed to use a different product ID for different devices, so you can uniquely identify them. I can't promise that every vendor handles this perfectly, any more than folks always ensured that PCI ids uniquely identified a specific hardware version, but one should blame the vendor for being brain-damaged in such cases; it isn't a fault of the USB standard If someone manufactures a single type of keyboard -- using only one type of ASIC, one PCB/keyswitch layout, one kind of housing, etc. -- I'd say it is very much open to interpretation whether snapping on a different collection of keycaps makes it into a different product. Even if the manufacturer tried to cover for the possibility, e.g. by providing a jumper on the PCB which is supposed to be set according to the installed set of keycaps, there will still be cases where an end user replaces or rearranges the keycaps to change the layout and doesn't change the jumper setting. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to persist tape configuration
Hello. I need to set my tape with: mt comp off. After a reboot I need to do this again. I could write a script and place it in /usr/local/etc/rc.d, but I'm just wondering if there's already something standard in /etc. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com, 2011-11-09 22:10 (+0100): How would HAL know that the keyboard had a Swedish layout? No such information is sent through USB or PS/2 when you attach a keyboard. True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. I'm sorry I was unclear. I meant the USB device doesn't say what physical keyboard layout it has in any standardized way. There is nothing in the USB protocol about it. The product ID code might tell you something if you have a large database and the USB product ID is indeed different between two physical layouts. It might not be. For instance, while ANSI keyboards and ISO keyboards are bound to have different USB product IDs because of actually physical differences in the number of keys, the only thing that differs between, say, a German keyboard and a Swedish keyboard of the same model is what is printed on the keycaps. A vendor might see these as the same USB product ID. -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Freebsd 6 and nfsstats counters
Hi, I have a bunch of old freebsd servers I want to collect nfs stats from. The problem is a lots of the counters have wrapped around. On other Freebsd 7+ machines I take care of this be a weekly cron of nfsstat -c -z. The z option isnt available in freebsd 6, and I cant see a direct sysctl OID i can reset. Has anyone encountered this issue in the past and found a fix. I'd rather avoid having to alter the scripts to cater for negative numbers. k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
Hi All I'm trying to upgrade from FreeBSD 8.0-RELEASE #0 to FreeBSD 8.2 or better. My upgrade sequence would be as follows: 0. cd /usr/src/;make cleanworld (and in extreme cases rm -rf /usr/src/* and rm -rf /usr/obj) 1. csup -L 2 stable supfile. 2. cd /usr/src; make buildworld make buildkernel make installkernel make installworld reboot 3. mergemaster -p make installworld mergemaster reboot My stable-supfile is as follows: --- *default host=cvsup2.za.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8_2 *default delete use-rel-suffix src-all --- However, I'm not getting past make buildworld. Below is the tail end of my make buildworld: --- . . . cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- My questions are: - Is this a known issue (can't seem to find much on google) ? - If not, how would I go about pinpointing the root cause of this compile error. Upping the make debug level doesn't seem to get my any more detailed information that I can use . I've run csup multiple times (with multiple make clean;make cleanworld;make cleandir in between) across 48 hours , but each update to my source tree doesn't seem to get any different result. I've also tried upgrading my userland tools before doing the upgrade (portupgrade -a) in the hope that the my compiler tools might have been updated to fix this. Any advice would be appreciated, Traiano ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Samuel Magnusson samuel.magnuss...@bredband.net, 2011-11-09 21:52 (+0100): Because with HAL and DBUS enabled this InputDevice section is bypassed unless I also specify Option AutoAddDevices false. Which I understand gives the same result as not enabling HAL and DBUS in the first place. If you don't enable HAL and DBUS, you're using an X server compiled with HAL and DBUS support and you haven't set AutoAddDevices to false you won't get any input devices at all: no working mouse, no working keyboard. At least, this was my experience after an upgrade long ago. Quite frustrating. I learned about the AutoAddDevices first and later rebuilt my X server without HAL or DBUS support. -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Samuel Magnusson samuel.magnuss...@bredband.net, 2011-11-10 00:49 (+0100): Michael Cardell Widerkrantz wrote 2011-11-09 21:02: What new style XML method? I'm referring to what Polytropon said about all the new stuff required by X. As I understood him he was talking about the XML-files to give directions to HAL Ah! HAL! Good riddance! Perhaps you can file a Problem Report (PR) with a suggested text? I suggest you add the text to the handbook since I assume the X.org project won't touch manual pages for the ancient X servers we use in FreeBSD. As I understand you, the man-pages from Xorg that are in FreeBSD are not allowed to be altered unless the Xorg project do it themselves, I'm sure they can be altered in FreeBSD. I just thought it might be better to add the text to the handbook. Or both. Anyway, I wasn't aware that the FreeBSD X server was ancient and different from any other. :) We're a few versions behind the X.org bleeding edge since modern servers require kernel changes. Modern X.org servers require Kernel-based Mode Setting (KMS) and Graphics Execution Manager (GEM) and udev support. While it's likely there could be some udev glue on top of devd I don't know if someone is working on it. Warner, perhaps? KMS and GEM, mainly for the intel drivers, are being worked on: http://wiki.freebsd.org/Intel_GPU Also a good beginners tutorial on the fonts would be good, because as I understand it there is also an old and a new way with the core fonts and the font server, some methods belonging to one and some to the other. That's true. You can start by reading my blog post about it: http://hack.org/mc/blog/xfonter.html It's in Swedish, I'm afraid, but both your name and the fact that you were talking about a Swedish keyboard earlier makes me think you can cope with that. But if I do produce something, where should I send the PR and text? See the send-pr(1) manual page. Failing that, use: http://www.freebsd.org/send-pr.html -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sed vs gnu sed
On 10/11/2011 07:00, per...@pluto.rain.com wrote: Vincent Hoffmanvi...@unsane.co.uk wrote: bsd sed (correctly according to SUS at least, I believe[1]) appends a newline when writing to standard out, gnu sed doesnt. The wonderful thing about standards is that there are so many to choose from -- Tanenbaum is there any easy way to make our sed do the same as gnu sed here? As long as it is OK to remove _all_ newlines -- which seems to be the case here -- you could pipe the output through tr -d '\012' Thanks to all for suggestions, I'll move to using tr at some point i think but the overhead of any of the approaches is pretty negligable (except for firing up python/perl ;) Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Polytropon free...@edvax.de, 2011-11-10 01:30 (+0100): Now as it (almost?) works on FreeBSD, it's already deprecated by new Linux concepts such as udev, upower and other usomethings. Maybe they become available as interfaces on FreeBSD too, but my fear is... as soon as they are usable, there's already something else obsoleting them right away. :-( By then I'm sure Linux distributions have moved on to the Wayland Display System. Times like these I wish I had the time to bring back MGR from the dead: http://hack.org/mc/mgr/ -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 2011/11/10 at 18:05, Traiano Welcome traiano.welc...@mtnbusiness.co.za wrote: Hi All I'm trying to upgrade from FreeBSD 8.0-RELEASE #0 to FreeBSD 8.2 or better. My upgrade sequence would be as follows: 0. cd /usr/src/;make cleanworld (and in extreme cases rm -rf /usr/src/* and rm -rf /usr/obj) 1. csup -L 2 stable supfile. 2. cd /usr/src; make buildworld make buildkernel make installkernel make installworld reboot 3. mergemaster -p make installworld mergemaster reboot No. your upgrade steps are a little bit wrong. Just follow this: build world - build kernel - install kernel - reboot to singler user - mergemaster -p - install world - mergemaster - make delete-old ... You'd better take a look at /usr/src/UPGRADING, which contains details about upgrade steps. My stable-supfile is as follows: --- *default host=cvsup2.za.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8_2 *default delete use-rel-suffix src-all --- However, I'm not getting past make buildworld. Below is the tail end of my make buildworld: --- . . . cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- My questions are: - Is this a known issue (can't seem to find much on google) ? - If not, how would I go about pinpointing the root cause of this compile error. Upping the make debug level doesn't seem to get my any more detailed information that I can use . I've run csup multiple times (with multiple make clean;make cleanworld;make cleandir in between) across 48 hours , but each update to my source tree doesn't seem to get any different result. I've also tried upgrading my userland tools before doing the upgrade (portupgrade -a) in the hope that the my compiler tools might have been updated to fix this. Any advice would be appreciated, Traiano -- History proves nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
2011-11-09 21:52, Samuel Magnusson skrev: When I first installed Xorg I began by following the handbook, which means that I unwittingly did this to my poor rc.conf: hald_enable=YES dbus_enable=YES That meant that I would HAVE to go into the XML-stuff (to get swedish keys) If all you want is a swdish keyboard layout then put this in your ~/.xinitrc setxkbmap se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
Hi Thanks for the feedback. On 2011/11/10 1:28 PM, Denise H. G. darc...@gmail.com wrote: On 2011/11/10 at 18:05, Traiano Welcome traiano.welc...@mtnbusiness.co.za wrote: Hi All I'm trying to upgrade from FreeBSD 8.0-RELEASE #0 to FreeBSD 8.2 or better. My upgrade sequence would be as follows: 0. cd /usr/src/;make cleanworld (and in extreme cases rm -rf /usr/src/* and rm -rf /usr/obj) 1. csup -L 2 stable supfile. 2. cd /usr/src; make buildworld make buildkernel make installkernel make installworld reboot 3. mergemaster -p make installworld mergemaster reboot No. your upgrade steps are a little bit wrong. Just follow this: build world - build kernel - install kernel - reboot to singler user - mergemaster -p - install world - mergemaster - make delete-old ... I'd be happy to try this sequence, however I don't make it past make buildworld. (of note, the sequence I used above works on all my other boxen though) I've just scrutinised /usr/src/UPDATING (there is no file called UPGRADING ? ) and can't seem to find anything specific to this make fail. File version as follows: $FreeBSD: src/UPDATING,v 1.632.2.19.2.6 2011/10/04 19:07:38 cperciva Exp $ I'm following the process outlined in the FreeBSD manual up until make buildworld, and can't see where I might be wrecking things: 1) synching the source: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html (... BTW, note to editor: I see nothing in this section of the manual about csup? 2) building world: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html BTW: I've just upgraded my binutils (as, ld) as there was a reference in the UPDATING file to an ld bug, but that did not seem to affect anything. You'd better take a look at /usr/src/UPGRADING, which contains details about upgrade steps. My stable-supfile is as follows: --- *default host=cvsup2.za.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8_2 *default delete use-rel-suffix src-all --- However, I'm not getting past make buildworld. Below is the tail end of my make buildworld: --- . . . cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/inclu de -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- My questions are: - Is this a known issue (can't seem to find much on google) ? - If not, how would I go about pinpointing the root cause of this compile error. Upping the make debug level doesn't seem to get my any more detailed information that I can use . I've run csup multiple times (with multiple make clean;make cleanworld;make cleandir in between) across 48 hours , but each update to my source tree doesn't seem to get any different result. I've also tried upgrading my userland tools before doing the upgrade (portupgrade -a) in the hope that the my compiler tools might have been updated to fix this. Any advice would be appreciated, Traiano -- History proves nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 11/10/11 11:05 AM, Traiano Welcome wrote: Hi All I'm trying to upgrade from FreeBSD 8.0-RELEASE #0 to FreeBSD 8.2 or better. My upgrade sequence would be as follows: 0. cd /usr/src/;make cleanworld (and in extreme cases rm -rf /usr/src/* and rm -rf /usr/obj) 1. csup -L 2 stable supfile. 2. cd /usr/src; make buildworld make buildkernel make installkernel make installworld reboot 3. mergemaster -p make installworld mergemaster reboot Your upgrade steps are wrong, although this has nothing to do with your buildworld failing. 1/ make buildworld (automatically cleans up anyway) 2/ make buildkernel 3/ make installkernel 4/ mergemaster -p 5/ reboot (single user if possible) 6/ make installworld 7/ mergemaster -F 8/ reboot 9/ optional, make delete-old Why use csup manually ? Set your variables in /etc/make.conf and just run make update from /usr/src. Here are mine: SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -zgL 2 SUPHOST=cvsup1.fr.freebsd.org SUPFILE=/etc/cvsup/stable-supfile PORTSSUPFILE= /etc/cvsup/ports-supfile DOCSUPFILE= /etc/cvsup/doc-supfile == Post your src.conf and make.conf, your problem might be there. As a last resort, I would suggest synching sources with 8.1 and trying to build it, to see if you still encounter the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
Damien Fleuriot schreef: Here are mine: SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -zgL 2 SUPHOST=cvsup1.fr.freebsd.org SUPFILE=/etc/cvsup/stable-supfile PORTSSUPFILE= /etc/cvsup/ports-supfile DOCSUPFILE= /etc/cvsup/doc-supfile There is no -g anymore for csup, so SUPFLAGS= -zL2 would do. regards Johan Hendriks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 2011/11/10 at 20:56, Traiano Welcome traiano.welc...@mtnbusiness.co.za wrote: Hi Thanks for the feedback. I'd be happy to try this sequence, however I don't make it past make buildworld. (of note, the sequence I used above works on all my other boxen though) I've just scrutinised /usr/src/UPDATING (there is no file called UPGRADING ? ) and can't seem to find anything specific to this make fail. File version as follows: Sorry, it's a typo. It IS UPDATING not UPGRADING:) If you still can't make it, there probably are some problems with your system. Or you could clean up everything, re-csup your system sources and try again. Or you could file a bug report to see if it helps. $FreeBSD: src/UPDATING,v 1.632.2.19.2.6 2011/10/04 19:07:38 cperciva Exp $ I'm following the process outlined in the FreeBSD manual up until make buildworld, and can't see where I might be wrecking things: 1) synching the source: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html (... BTW, note to editor: I see nothing in this section of the manual about csup? csup is a C language rewrite of cvsup. Generally you could tell no difference between them from a user's perspective. 2) building world: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html BTW: I've just upgraded my binutils (as, ld) as there was a reference in the UPDATING file to an ld bug, but that did not seem to affect anything. I think this might be irrelevant to your case. -- History proves nothing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On Thu, Nov 10, 2011 at 10:05:27AM +, Traiano Welcome wrote: Hi All I'm trying to upgrade from FreeBSD 8.0-RELEASE #0 to FreeBSD 8.2 or better. My upgrade sequence would be as follows: 0. cd /usr/src/;make cleanworld (and in extreme cases rm -rf /usr/src/* and rm -rf /usr/obj) 1. csup -L 2 stable supfile. 2. cd /usr/src; make buildworld make buildkernel make installkernel make installworld reboot 3. mergemaster -p make installworld mergemaster reboot My stable-supfile is as follows: --- *default host=cvsup2.za.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8_2 *default delete use-rel-suffix src-all --- However, I'm not getting past make buildworld. Below is the tail end of my make buildworld: --- . . . cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- My questions are: - Is this a known issue (can't seem to find much on google) ? - If not, how would I go about pinpointing the root cause of this compile error. Upping the make debug level doesn't seem to get my any more detailed information that I can use . I've run csup multiple times (with multiple make clean;make cleanworld;make cleandir in between) across 48 hours , but each update to my source tree doesn't seem to get any different result. I've also tried upgrading my userland tools before doing the upgrade (portupgrade -a) in the hope that the my compiler tools might have been updated to fix this. Any advice would be appreciated, Traiano Can you supply us with: $ uname -a $ cc -v $ cat /etc/make.conf Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpvMQHm2oAGP.pgp Description: PGP signature
Fwd: changing baud rate without recompiling
On Thu, Nov 10, 2011 at 11:48 AM, saeedeh motlagh saeedeh.motl...@gmail.com wrote: hi thanks for your answer. the output of ps ax | grep getty is: 1357 u0 Is+0:00.00 /usr/libexec/getty std.115200 ttyu0 i think it's true. isn't it? but the stty -f /dev/ttyu0 shows 9600 and can't have communication with the other system by 115200 baud rate. i check my gettytab file too. actually i don't understand what these commands mean. some of commands are: std.115200|115200-baud:\ :np:sp#115200: P|Pc|Pc console:\ :ht:np:sp#115200:\ :cl=\E[H\E[2J: al.115200:\ :al=root:tc=std.115200: what is the exactly command that i should have in this file? IMHO, that's correct. there is no special command for baud rate in /etc/login.conf it's so necessary for me to change my baud rate so please help me if you know what should i do. thanks I don't know. Could you please CC the list, maybe someone else has an idea? Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sed vs gnu sed
On 10 November 2011 10:33, Vincent Hoffman vi...@unsane.co.uk wrote: On 10/11/2011 07:00, per...@pluto.rain.com wrote: Vincent Hoffmanvi...@unsane.co.uk wrote: bsd sed (correctly according to SUS at least, I believe[1]) appends a newline when writing to standard out, gnu sed doesnt. The wonderful thing about standards is that there are so many to choose from -- Tanenbaum is there any easy way to make our sed do the same as gnu sed here? As long as it is OK to remove _all_ newlines -- which seems to be the case here -- you could pipe the output through tr -d '\012' Thanks to all for suggestions, I'll move to using tr at some point i think but the overhead of any of the approaches is pretty negligable (except for firing up python/perl ;) Vince __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org you could sidestep the issue entirely /usr/ports/textproc/gsed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
On Nov 10, 2011, at 2:25 AM, Michael Cardell Widerkrantz wrote: True for PS/2, but not true for USB-- the USB Vendor Product ID can identify different keyboard types and let you infer the country. I'm sorry I was unclear. I meant the USB device doesn't say what physical keyboard layout it has in any standardized way. There is nothing in the USB protocol about it. That's fairly said-- you'd have to query a database of vendor+product ids and see whether you can determine that a particular keyboard is for a given country and/or language. If you don't find a match, there isn't a good way of identifying the region of the device just via USB protocol. The product ID code might tell you something if you have a large database and the USB product ID is indeed different between two physical layouts. It might not be. For instance, while ANSI keyboards and ISO keyboards are bound to have different USB product IDs because of actually physical differences in the number of keys, the only thing that differs between, say, a German keyboard and a Swedish keyboard of the same model is what is printed on the keycaps. A vendor might see these as the same USB product ID. Different keycaps means a different product SKU, at least. If they use the same USB product ID, then you're going to have to define a keymap file / xmodmap / etc to associate the scan codes with the right character that's printed on the keycaps. FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. To my mind, though, that's a fallback for when you have a KVM or a PS/2-to-USB converter or suchlike in the way that prevents the device from being correctly recognized. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
Chuck Swiger cswi...@mac.com, 2011-11-10 20:12 (+0100): Different keycaps means a different product SKU, at least. If they use the same USB product ID Yes. I think this is a quite common scenario. FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. Certainly. To my mind, though, that's a fallback for when you have a KVM or a PS/2-to-USB converter or suchlike in the way that prevents the device from being correctly recognized. Or when you have, say, a keyboard that physically is an ANSI keyboard (one less physical key compared to ISO keyboards) but still want, say, a Swedish keymap or, indeed, your very own keymap, unlike any other. Like me when I'm using one of my Happy Hacking Keyboards. Topre switches FTW! -- http://hack.org/mc/ Plain text e-mails, please. HTML messages sent to me are silently deleted. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.2 to 8.2 buildkernel fails (Suspect ignorance...)
Hi All: I attempting to build an 8.2 kernel on a 7.2 machine. I suspect that something need to be ipdated first, but don't no exactly what. It says inline functions are not supported; using GNU89. I get the following: = cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict- prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual - Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/ usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 -- param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack- boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding - fstack-protector -Werror /usr/src/sys/netinet/tcp_input.c cc1: warnings being treated as errors /usr/src/sys/netinet/tcp_input.c:385: warning: C99 inline functions are not supported; using GNU89 /usr/src/sys/netinet/tcp_input.c:385: warning: to disable this warning use - fgnu89-inline or the gnu_inline function attribute *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. = Any Ideas? Thanx, Gene -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On Thu, Nov 10, 2011 at 10:05:27AM +, Traiano Welcome wrote: [snip] cc -O2 -pipe -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/tmp/usr\ -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- Another question worth asking: how much memory/swap does the machine have? If FreeBSD runs short of memory, it will start killing processes. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpJifom8hqvp.pgp Description: PGP signature
Re: 7.2 to 8.2 buildkernel fails (Suspect ignorance...)
On Thu, Nov 10, 2011 at 1:02 PM, Gene f...@brightstar.bomgardner.net wrote: Hi All: I attempting to build an 8.2 kernel on a 7.2 machine. I suspect that something need to be ipdated first, but don't no exactly what. It says inline functions are not supported; using GNU89. I get the following: = cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict- prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual - Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/ usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 -- param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack- boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding - fstack-protector -Werror /usr/src/sys/netinet/tcp_input.c cc1: warnings being treated as errors /usr/src/sys/netinet/tcp_input.c:385: warning: C99 inline functions are not supported; using GNU89 /usr/src/sys/netinet/tcp_input.c:385: warning: to disable this warning use - fgnu89-inline or the gnu_inline function attribute *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. = Any Ideas? Thanx, Gene To get the basics out of the way, did you make buildworld first? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: changing baud rate without recompiling
On 9/11/2011 11:11 πμ, saeedeh motlagh wrote: i know adding the COM_CONSOLE_SPEED=115200 to make.conf and recompile it, change the baud rate but i want to know if there is a way to change it without recompiling. please let me know if there is any way to do that. my FreeBSD is 8.0 thanks. I am using a serial console at 115200 bps. Like you, I've added comconsole_speed=115200 to /boot/loader.conf and nothing happened. After booting, the serial terminal works at 115200 - but that's because of the /etc/ttys entry (which of course is not used until the end of booting). For the actual console to work at this speed so you can see the boot messages, it seems the only way is to recompile and reinstall the boot blocks. This takes very little time however: # cd /usr/src/sys/boot # make clean # make BOOT_COMCONSOLE_SPEED=115200 # make install No need to recompile the kernel or any other part of the base system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 7.2 to 8.2 buildkernel fails (Suspect ignorance...)
On Thu, 10 Nov 2011 13:36:54 -0600, Reid Linnemann wrote On Thu, Nov 10, 2011 at 1:02 PM, Gene f...@brightstar.bomgardner.net wrote: Hi All: I attempting to build an 8.2 kernel on a 7.2 machine. I suspect that something need to be ipdated first, but don't no exactly what. It says inline functions are not supported; using GNU89. I get the following: = % Snip To get the basics out of the way, did you make buildworld first? See! Ignorance... well, actually - forgetfulness. I've done this a dozen times before and I forgot? Sheesh. Thanks Gene ___ -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
On Thu, Nov 10, 2011 at 11:12 AM, Chuck Swiger cswi...@mac.com wrote: FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. I thought I'd mention that OS X takes an interesting approach to this. When you plug in a keyboard it doesn't recognize, it does a little dance where it tells you to press certain keys (e.g., Press the key to the right of the left Shift key, with a little graphic to help you understand which key it means) and from the results it infers the layout. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: DBUS + kvm breaks X server (was: X server and xinit works excellent....almost.)
On Wed, Nov 9, 2011 at 11:56 AM, Warren Block wbl...@wonkity.com wrote: Are the keyboard and mouse USB devices? A KVM should not disconnect them on switching, but maybe it does. In my experience, most inexpensive USB KVMs work by disconnecting the keyboard/mouse from one system and reconnecting them to the other. They rely on the OS's USB hotplug support to do the right thing. On Windows systems this is pretty obvious because you hear the ba-DUMP sound effect it makes when it detects a new USB device. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Still stalls on xpt_config
Every 9.0 version I've tried has failed to boot, ending up with:
Still waiting after {60,..,300} seconds for xpt_config.
What's a body to do? I've tried disabling ACPI, going single,
safe mode. All on my ASUS M4A785TD-EVO mobo with some amd64 x4.
Any additional info I can provide?
Very thankful for previous help. Hope somebody here can help.
Chuck Bacon -- c...@cape.com
ABHOR SECRECY -- DEFEND PRIVACY
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X server and xinit works excellent....almost.
On Nov 10, 2011, at 3:57 PM, David Brodbeck wrote: On Thu, Nov 10, 2011 at 11:12 AM, Chuck Swiger cswi...@mac.com wrote: FreeBSD's users generally are more technically inclined and might be willing to deal with this, but even so, I suspect that most folks would appreciate the system trying to figure out that an AZERTY keyboard layout means French, that JIS means Japanese, that QWERTZ probably indicates German / Swiss / Hungarian, etc. I thought I'd mention that OS X takes an interesting approach to this. When you plug in a keyboard it doesn't recognize, it does a little dance where it tells you to press certain keys (e.g., Press the key to the right of the left Shift key, with a little graphic to help you understand which key it means) and from the results it infers the layout. Indeed, yes-- that's KeyboardTypeSection, part of Setup Assistant.app used to perform initial configuration of a new system. While I think it makes a good example, I don't want to evangelize stuff from $REALJOB too strongly. :-) Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Unprintable 8-bit characters
On Tue, 8 Nov 2011 23:04:25 -0600 (CST) Robert Bonomi bon...@mail.r-bonomi.com wrote: Conrad J. Sabatier conr...@cox.net wrote: grin Yes, and this is one area where the labels are more than a little misleading as well. My natural inclination is think of UTF-8 as being a single-byte representation for each character in the set, whereas UTF-16, as the name implies, would be the wide, 2-byte version. Not exactly. Nonetheless, as I posted earlier in this thread, according to the info in gucharmap, the representations of the umlauted u are just the opposite of this: not exactly. Again. UTF-8: 0xC3 0xBC UTF-16: 0x00FC Go figure, huh? :-) In UTF-16, everything _is_ a 16-bit entity. Notice that 0x00FC has -four- nybbles after the '0x.' Every character boundary is on a multiple of 16 bits. Ah yes! I hadn't noticed that. What's really weird, as I mentioned in a later private email to Polytropon, last night, the copy-and-paste in gucharmap suddenly decided to start copying the UTF-8 code instead of the UTF-16. I have no idea why that changed. In UTF-8, the 'base' charset -- the 'C0' and 'C1' groups are represented by a single byte. 'extended' characters are represented by two bytes. Thus, 'characters' have a *variable*length* representation -- one or two bytes. A character, whether it is represented by one or two bytes, can begin on -any- byte boundary within a data stream, depending on 'what came before it'. UTF-8 2-byte representations are designed such that one can jump to any _byte_ offset within the file, and determine -- by looking *only* at the value of that byte whether is is (a) a single-byte character, (b) the first byte of a two-byte sequence, or (c) the second byte of a two-byte sequence. With UTF-16 you can position directly to any -character-, by jumping to a _byte_ offset that is twice the index of the character you want. Given a byte offset, you always know the 'equivalent' _character_ offset. With UTF-8, you have to read the character stream, counting 'characters' as you go, to get to the desired point. You can seek to an arbitrary _byte_ offset, but you do not know how mny 'characters' into the file that offset is. I see. Yes, that could certainly complicate things. UTF-8 vs. UTF-16 is a trade-off between 'compactness' (UTF-8), and simplicity of addessing/representation (UTF-16). This seems rather unfortunate to me. You would think that, by now, some standard character set might have emerged that would allow one to use, at the very least, the Western characters (as opposed to the Eastern or Oriental or Asian, if you will) with a reasonable expectation that others will see what was intended. Heh. How many 'character' codes are you willing to devote to national 'currency symbols', just for starters? Probable minimum of two per currency -- one for the minimum coinage unit (cent, pence, pfennig, etc.) and one for the denomination unit (dollar, pound, mark, kroner, etc.) Now, one (obviously) has to have the basic 'Roman' alphabet. Then there are all the diacritical markings (accent, accent grave, dot umlaut, ring, bar, 'hat', inverted hat, etc.) for vowels. And cedilla, tilde, etc., for select consonants. Plus language specific symbols like ess-zett , 'thorn', etc. How about phonetic symbols, like 'schwa' ? And Greek for all sorts of scientific use? What about Cyrilic characters, for many Eastern Eurpean languages? Now, consider punctuation marks: the 'typewriter' basics, How many of 'minus-sign, hyphen, em-dash, en-dash, soft-hyphen' are needed? How many of 'accent, accent grave, apostrophe, opening/closing single-quote' are needed? opening/closing double-quotes, and/or a 'position neutral' double-quote? Other symbols, like -- digits, common fractions, 'Trademark','Registered trademark','copyright' 'paragraph','section', superscripts -- exponents, footnotes, etc. subscripts -- chemical formulae, etc. Simple line-drawing graphics Diphthongs?? Ligatures?? Start counting things up. An 8-bit 'address space' gets used used up _really_ quick. wry grin I certainly get the point. :-) Thanks for that very thorough elucidation. :-) Now I just have to figure out what the heck's going on here, why suddenly I'm seeing the exact opposite of what I was seeing yesterday. Thought I had everything straightened out for a while there. :-( Oh, this is madness! :-) -- Conrad J. Sabatier conr...@cox.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
