8.2-RC Kernel build failure
cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/dev/jme/if_jme.c *** Error code 1 Stop in /usr/obj/usr/src/sys/GW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ 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: 8.2-RC Kernel build failure
On Sat, Jan 29, 2011 at 12:30 PM, Boris Samorodov b...@ipt.ru wrote: On Sat, 29 Jan 2011 12:19:00 +0300 Odhiambo Washington wrote: cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/dev/jme/if_jme.c *** Error code 1 Stop in /usr/obj/usr/src/sys/GW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It's always a good idea to show a command one used. And assuming you use -j X the log is useless since the actual error was way earlier. Please, remove the flag, add -DNO_CLEAN and show the command and a tail of the output. I always use `make kernel KERNCONF=MY_KERNEL`. No special flags. The whole output is here - http://62.8.64.102/~wash/kernel-20110129.log.txt http://62.8.64.102/~wash/kernel-20110129.log.txt -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ 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: 8.2-RC Kernel build failure
On Sat, 29 Jan 2011 12:19:00 +0300 Odhiambo Washington wrote: cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/dev/jme/if_jme.c *** Error code 1 Stop in /usr/obj/usr/src/sys/GW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It's always a good idea to show a command one used. And assuming you use -j X the log is useless since the actual error was way earlier. Please, remove the flag, add -DNO_CLEAN and show the command and a tail of the output. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! Yep. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 8.2-RC Kernel build failure
On Sat, 29 Jan 2011 12:49:10 +0300 Odhiambo Washington wrote: On Sat, Jan 29, 2011 at 12:30 PM, Boris Samorodov b...@ipt.ru wrote: On Sat, 29 Jan 2011 12:19:00 +0300 Odhiambo Washington wrote: cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/dev/jme/if_jme.c *** Error code 1 Stop in /usr/obj/usr/src/sys/GW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It's always a good idea to show a command one used. And assuming you use -j X the log is useless since the actual error was way earlier. Please, remove the flag, add -DNO_CLEAN and show the command and a tail of the output. I always use `make kernel KERNCONF=MY_KERNEL`. No special flags. The whole output is here - http://62.8.64.102/~wash/kernel-20110129.log.txt http://62.8.64.102/~wash/kernel-20110129.log.txt As for me, I've seen that for the first time... First I'll try to cleandir and redo the build. If fail -- build GENERIC, if fail -- GENERIC with null make.conf. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: missing us.dvorakr.kbd
On Fri, 28 Jan 2011 14:28:09 -0800 (PST) Neil Short nesh...@yahoo.com wrote: us.dvorakr.kbd is missing from /usr/share/syscons/keymaps/ I found one on the web; but wonder if it's been fixed. $ uname -a FreeBSD carmen.opera 8.1-STABLE FreeBSD 8.1-STABLE #2: Wed Oct 13 20:48:24 MST 2010 neshort@carmen:/usr/obj/usr/src/sys/CARMEN amd64 Actually it's already present in /usr/src/share/syscons/keymaps, but for some reason it doesn't get installed. -- Gary Jennejohn ___ 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: syslog and chrooted isc-dhcpd
On 01/28/2011 09:22 AM, Michael wrote: I'm running my isc-dhcp41-server with chroot option. Is it possible to get it working with syslog? I don't know how to let chrooted dhcpd to talk with my syslog. Apparently, you can either provide the -l flag via rc.conf (syslogd_flags) or add the full log socket path to /var/run/syslogd.sockets on the host. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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
pop-up
I keep getting a pop-up on my computer that reads unexpected error has occurred ESOAPHTTP exception a connection w/ server could not be established Url:http bootstrap developement how can i remove as pop up thank you JJkenyon ___ 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
bigbluebutton
I've managed to build a partially working bigbluebutton (bigbluebutton-0.71_1) conference server on 9.0-Current, 8.2 Pre-Release and 7.3 stable platforms. On all versions of FreeBSD, I'm having the same issues, they are: 1. audio conferencing between web-joined users only works with asterisk 14. (14.39.1 sources --14.37 in ports is flagged for a security problem) I have no conference audio with asterisk16 or asterisk18 2. In the presentation module, Only one page of a document is ever displayed and only one thumbnail is ever created. The video camera sharing, the Desktop sharing, the whiteboard, and the built in text chat all seem to work fine. Does anyone have any similar experiences or solutions? Thanks Tim Kellers ___ 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: /usr/ports/x11-wm/awesome problems
On Fri, Jan 28, 2011 at 09:08:36PM -0800, Joseph Olatt wrote: Hi, Anybody on the list having recent problems with the awesome window manager? I get the following error when I try to run awesome: W: awesome: image_new_from_file:288: cannot load image /usr/local/share/awesome/icons/awesome16.png: unknown error, that's really bad /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare number with nil W: awesome: image_new_from_file:288: cannot load image /usr/local/share/awesome/icons/awesome16.png: unknown error, that's really bad /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare number with nil /usr/local/share/awesome/icons/awesome16.png exists, is readable and can be displayed fine with display(1). I did csup the ports tree and recompiled both awesome and imlib2, but did not succeed. The entire output of startx is: X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-PRERELEASE i386 Current Operating System: FreeBSD mint 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0: Fri Jan 21 05:05:00 CST 2011 root@mint:/usr/obj/usr/src/sys/MINT i386 Build Date: 27 January 2011 07:56:40PM Current version of pixman: 0.18.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Jan 28 21:43:23 2011 (==) Using default built-in configuration (30 lines) (EE) Failed to load module fbdev (module does not exist, 0) NTSC XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_DAC1 DDC reg: 0x60 XRANDR name: DVI-0 Connector: DVI-D DFP1: INTERNAL_TMDS1 DDC reg: 0x64 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVDS DDC reg: 0x6c XRANDR name: S-video Connector: S-video TV1: INTERNAL_DAC2 DDC reg: 0x0 finished output detect: 0 finished output detect: 1 finished output detect: 2 finished output detect: 3 finished all detect Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable primary dac disable FP1 disable TV init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable FP1 disable TV record: RECORD extension enabled at configure time. record: This extension is known to be broken, disabling extension now.. record: http://bugs.freedesktop.org/show_bug.cgi?id=20500 W: awesome: image_new_from_file:288: cannot load image /usr/local/share/awesome/icons/awesome16.png: unknown error, that's really bad /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare number with nil W: awesome: image_new_from_file:288: cannot load image /usr/local/share/awesome/icons/awesome16.png: unknown error, that's really bad /usr/local/share/awesome/lib/awful/menu.lua:221: attempt to compare number with nil E: awesome: main:505: couldn't find any rc file Missing rc file. Copy and edit the example one distributed in the package/port to your $HOME. Hopefully, that will get rid of most of the warnings. waiting for X server to shut down xmessage: not found xmessage: not found finished PLL2 finished PLL1 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ 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: PF firewall rules and documentation
On 01/29/11 23:50, Iñigo Ortiz de Urbina wrote: I think that kind of user should never be in charge of anything security related Reading my own post I realise I forgot my question due to kiddie issues that were occuring in my vicinity. That is, how would one go about this? As for user suitability, how else does one learn if not through practice? On 1/29/11, Da Rockfreebsd-questi...@herveybayaustralia.com.au wrote: I spent some time playing with pf and pf.conf, and followed the directions in the handbook. It redirected me to the openbsd site for pf.conf, and recommended it as the most comprehensive documentation for pf. Firstly, I didn't find that. I had to translate the instructions into the current version used in FreeBSD, OpenBSD appears to be further advanced than this based on the current docs. Secondly, some of the rules don't appear to be following. From my understanding based on the documentation in the handbook and on the site pf is default allowing traffic. So explicit rules to block should be set first and then rules set to allow what is needed in. Some assumptions are made in the rules by the interpreter, so according to OpenBSD one can (even in the older versions) simply state block and it is interpreted as 'block on $interfaces all'. This turned out to not be the case. I know this has come up before, but I think it might be time to document pf.conf properly. It seems to be a bit of security risk not to. Users may be mistaken in their belief of their security on the network using pf, and may be less likely to trust again when it breaks. Cheers ___ 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
