Question regarding /etc/src.conf
Hi I have a question about src.conf for buildworld: I would like to exclude building a number of modules which I do not need in world, so I cretated a file modex.conf in a new directory /etc/make. Then, in makefile.conf I tried placing: .include "/etc/make/modex.conf" WITHOUT_MODULES= "/etc/make/modex.conf" But neither works and the modules are still built. What would be the correct syntax for such a file? Thanks. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Question-regarding-etc-src-conf-tp5769677.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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: Question regarding /etc/src.conf
MODULES_OVERRIDE=ath ath_pci wlan ... or WITHOUT_MODULES= ... in make.conf traditionally, but should be possible with .include also. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Question-regarding-etc-src-conf-tp5769677p5769711.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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: Question regarding /etc/src.conf
On Sun, 16 Dec 2012 09:14:38 +0100, Beeblebrox wrote: Hi I have a question about src.conf for buildworld: I would like to exclude building a number of modules which I do not need in world, so I cretated a file modex.conf in a new directory /etc/make. Then, in makefile.conf I tried placing: .include "/etc/make/modex.conf" WITHOUT_MODULES= "/etc/make/modex.conf" But neither works and the modules are still built. What would be the correct syntax for such a file? Thanks. Do you use /etc/makefile.conf or /etc/make.conf? I think it helps if you copy paste your files in your email. Ronald. ___ 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: thinkpad and synaptics
On 12/16/12 02:40, Zoran Kolic wrote: Lenovo e320, 9.1, amd64. Installed synaptics driver and tried out almost all configurations available on the net. None works. Including hw.pci.synaptics_support in loader.conf, gives psm0 in /dev. Shouldn't it be "hw.psm.synaptics_support" instead? Changing InputDevice in xorg.conf simply made me mad. Like this: InputDevice "Synaptics-Touchpad" "Corepointer" Identifier "Touchpad0"` Driver "synaptics" Option "Protocol" "psm" Option "Device" "/dev/psm0" Etc, etc. Should I add something more or I'm on a wrong path? Best regards Zoran ___ 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" ___ 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: thinkpad and synaptics
> > Including hw.pci.synaptics_support in loader.conf, gives psm0 in /dev. > > Shouldn't it be "hw.psm.synaptics_support" instead? Yes. It was typo. People simply report success in having vertical scroll on thinkpads. Whatever I tried out, failed. Frankly, every link I found did not look similar one to another. Use moused, remove moused. Include mouse0, re- place mouse0 with touchpad0. Include VerticalScroll (or else), just let it plain. I cannot follow them all. Best regards Zoran ___ 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: thinkpad and synaptics
Yea scrolling touchpad is a nice option, I want it too on my Dell Latitude 4310 :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: thinkpad and synaptics
On Sun, 16 Dec 2012 06:40:53 +0100 Zoran Kolic wrote: > Lenovo e320, 9.1, amd64. > Installed synaptics driver and tried out almost all configurations > available on the net. None works. > Including hw.pci.synaptics_support in loader.conf, gives psm0 in /dev. > Changing InputDevice in xorg.conf simply made me mad. Like this: > > InputDevice "Synaptics-Touchpad" "Corepointer" > Identifier "Touchpad0"` > Driver "synaptics" > Option "Protocol" "psm" > Option "Device" "/dev/psm0" > > Etc, etc. > Should I add something more or I'm on a wrong path? > Best regards > > Zoran > works for me on head, amd64, lenovo ideapad b450: [tiger@laptop]:~%dmesg | grep psm psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 [tiger@laptop]:~%grep syn /boot/loader.conf hw.psm.synaptics_support=1 xorg.conf: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "synaptics" Option "Protocol" "psm" Option "Device" "/dev/psm0" Option "SHMConfig" "on" Option"MinSpeed" "7" Option"MaxSpeed" "9" Option"AccelFactor" "0.0015" Option "ZAxisMapping" "4 5 6 7" EndSection [tiger@laptop]:~%grep mouse /etc/rc.conf mousechar_start="3" #moused_enable="YES" [tiger@laptop]:~%pkg info -x input-s xf86-input-synaptics-1.5.0 X.Org synaptics input driver -- wbr, tiger ___ 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: thinkpad and synaptics
On Sun, 2012-12-16 at 16:18 +0100, Zoran Kolic wrote: > > > Including hw.pci.synaptics_support in loader.conf, gives psm0 in /dev. > > > > Shouldn't it be "hw.psm.synaptics_support" instead? > > Yes. It was typo. > People simply report success in having vertical scroll > on thinkpads. Whatever I tried out, failed. Had you tried set up it from boot.loader? > Frankly, every link I found did not look similar one to > another. Use moused, remove moused. Include mouse0, re- > place mouse0 with touchpad0. Include VerticalScroll (or > else), just let it plain. I cannot follow them all. > Best regards > > Zoran > > ___ > 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" signature.asc Description: This is a digitally signed message part
Question regarding /etc/src.conf
>> WITHOUT_MODULES= ... in make.conf traditionally
Exactly - that's why my /etc/make/modex.conf has:
WITHOUT_MODULES= aac acpi_asus acpi_dock acpi_fujitsu acpi_hp \
and on and on... I do not want to put this long list in the make.conf
because it makes that file a lot more complicated than necessary. So I
prefer to separate the list of excluded modules into a different file.
@Ronald_Klop: I use /etc/make.conf. A portion of that file is:
#.include "/etc/make/modex.conf"
#WITHOUT_MODULES= "/etc/make/modex.conf"
BUILDFLAGS= /usr/local/share/bsdadminscripts/buildflags.mk
.if exists(${BUILDFLAGS})
.include "${BUILDFLAGS}"
.endif
I also use /etc/src.conf for stuff like WITHOUT_PORTSNAP= yes,
WITHOUT_SENDMAIL= yes
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Question-regarding-etc-src-conf-tp5769677p5769816.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
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"
cvsup8.us problem
I run the below as part of a script to find the server to grab source from; It is just hanging at cvsup8.us; it isn't succeeding or erroring out. fastest_cvsup -c US >> Querying servers in countries: us --> Connecting to cvsup.us.freebsd.org [72.233.193.64]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 69.42 ms --> Connecting to cvsup2.us.freebsd.org [130.94.149.166]... * error: connect: timeout --> Connecting to cvsup3.us.freebsd.org [128.31.0.28]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 104.96 ms --> Connecting to cvsup4.us.freebsd.org [204.152.184.73]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 42.98 ms --> Connecting to cvsup5.us.freebsd.org [208.83.20.166]... - server replied: ! Access limit exceeded; try again later - time taken: 97.23 ms --> Connecting to cvsup6.us.freebsd.org [204.9.55.82]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 79.59 ms --> Connecting to cvsup7.us.freebsd.org [128.205.32.24]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 105.53 ms --> Connecting to cvsup8.us.freebsd.org [216.165.129.134]... ___ 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"
cvsup8.US problem
I run the below as part of a script to find the server to grab source from; It is just hanging at cvsup8.us; it isn't succeeding or erroring out. fastest_cvsup -c US >> Querying servers in countries: us --> Connecting to cvsup.us.freebsd.org [72.233.193.64]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 69.42 ms --> Connecting to cvsup2.us.freebsd.org [130.94.149.166]... * error: connect: timeout --> Connecting to cvsup3.us.freebsd.org [128.31.0.28]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 104.96 ms --> Connecting to cvsup4.us.freebsd.org [204.152.184.73]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 42.98 ms --> Connecting to cvsup5.us.freebsd.org [208.83.20.166]... - server replied: ! Access limit exceeded; try again later - time taken: 97.23 ms --> Connecting to cvsup6.us.freebsd.org [204.9.55.82]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 79.59 ms --> Connecting to cvsup7.us.freebsd.org [128.205.32.24]... - server replied: OK 17 0 SNAP_16_1h CVSup server ready - time taken: 105.53 ms --> Connecting to cvsup8.us.freebsd.org [216.165.129.134]... ___ 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"
Installworld failure on RELENG_9
Greetings, I've used BSD exclusively since the early 80's, and this is my first experience with a build(world|kernel) || install(world|kernel) fail. That said, after installing from a 9.0 CD && syncing src && ports, I began the process of building and installing a custom kernel, and building & installing world. kernel went as expected/anticipated. However, as buildworld (altho slow) went without incident, installworld failed: -- begin error output - /usr/src/lib/csu/i386-elf/crti.S:26:25 error: machine/asm.h: No such file or directory /usr/src/lib/csu/i386-elf/crti.S: Assembler messages: /usr/src/lib/csu/i386-elf/crti.S:27: Error: invalid character '_' in mnemonic *** Error code 1 Stop in /usr/src/lib/csu/i386-elf. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- end error output - Additional info: FreeBSD 9.1-PRERELEASE #0 Sun Dec 16 21:27:50 PST 2012 root@ns0:/usr/obj/usr/src/sys/GENERIC i386 The only difference (aside from BSD version) was the addition of clang. It took easily 3 times as long to complete world than past experience. :( Thank you for all your time, and consideration. --Chris ___ 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: Installworld failure on RELENG_9
On Sun, Dec 16, 2012 at 03:07:46PM -0800, Chris H wrote: > Greetings, > I've used BSD exclusively since the early 80's, and this is my first > experience with a build(world|kernel) || install(world|kernel) fail. > That said, after installing from a 9.0 CD && syncing src && ports, > I began the process of building and installing a custom kernel, and > building & installing world. > kernel went as expected/anticipated. However, as buildworld (altho slow) > went without incident, installworld failed: > You should run 'buildworld' first, because that creates the toolchain for the kernel build. Anyway, what does your custom kernel config contain? Please attach it. Glen pgpJgWGzW60ox.pgp Description: PGP signature
Re: Installworld failure on RELENG_9
Greetings Gary, and thank you for your reply. > On Sun, Dec 16, 2012 at 03:07:46PM -0800, Chris H wrote: >> Greetings, >> I've used BSD exclusively since the early 80's, and this is my first >> experience with a build(world|kernel) || install(world|kernel) fail. >> That said, after installing from a 9.0 CD && syncing src && ports, >> I began the process of building and installing a custom kernel, and >> building & installing world. >> kernel went as expected/anticipated. However, as buildworld (altho slow) >> went without incident, installworld failed: >> > > You should run 'buildworld' first, because that creates the toolchain > for the kernel build. Yes. That was the order I used (world, kernel),. Sorry if that wasn't clearer. > > Anyway, what does your custom kernel config contain? Please attach it. > > Glen > > Consider it done (see attached). FWIW: I synced src && ports yesterday (2012-12-15) from cvsup7.freebsd.org --Chris # # NS0 -- NS0 kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/NS0,v 1.6.2.16 2012/12/16 20:20:10 chrish Exp $ cpu I686_CPU ident NS0 makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCL # New Network Filesystem Client options NFSD# New Network Filesystem Server options NFSLOCKD# Network Lock Manager options NFS_ROOT# NFS usable as /, requires NFSCL options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_RAID # Soft RAID functionality. options GEOM_LABEL # Provides labelization options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options PRINTF_BUFR_SIZE=128# Prevent printf output being interspersed. options KBD_INSTALL_CDEV# install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework #optionsKDTRACE_HOOKS # Kernel DTrace hooks options INCLUDE_CONFIG_FILE # Include this file in kernel options KDB # Kernel debugger related code options KDB_TRACE # Print a stack trace for a panic # To make an SMP kernel, the next two lines are needed options SMP # Symmetric MultiProcessor Kernel device apic
How do I circumvent the use of clang during build?
Greetings, I recently made a attempt to move from RELENG_8 to RELENG_9. I've been on BSD since the early 80's, and with the exception of a couple of failed kernels (my fault), I've never had one failure with the build(world|kernel) || install(world|kernel). The only notable difference I noticed, was the addition of clang. While I can't (yet) conclusively blame it on clang. I _can_ say, that the whole process took _3_ times longer, than without. So my question is; is it possible to build(world|kernel) && install(world|kernel) without the clang toolchain? If for no other reason but to discover whether clang was responsible for the failure, and whether building w/o clang is any faster. Thank you for all your time, and consideration. --Chris ___ 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: How do I circumvent the use of clang during build?
As I understand it, gcc is still the default on 9 - Tim Daneliuk Chris H wrote: >Greetings, > I recently made a attempt to move from RELENG_8 >to RELENG_9. I've been on BSD since the early 80's, and with >the exception of a couple of failed kernels (my fault), I've >never had one failure with the build(world|kernel) || >install(world|kernel). The only notable difference I noticed, >was the addition of clang. While I can't (yet) conclusively >blame it on clang. I _can_ say, that the whole process took _3_ >times longer, than without. So my question is; is it possible >to build(world|kernel) && install(world|kernel) without the >clang toolchain? If for no other reason but to discover whether >clang was responsible for the failure, and whether building w/o >clang is any faster. > >Thank you for all your time, and consideration. > >--Chris > >___ >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" ___ 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: How do I circumvent the use of clang during build?
On 16 December 2012 21:17, Tim Daneliuk wrote: > As I understand it, gcc is still the default on 9 For the build, but clang is still built. > is it possible >>to build(world|kernel) && install(world|kernel) without the >>clang toolchain? make -DWITHOUT_CLANG -- Eitan Adler ___ 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: How do I circumvent the use of clang during build?
Greetings, and thank you for the response. > On 16 December 2012 21:17, Tim Daneliuk wrote: >> As I understand it, gcc is still the default on 9 > > For the build, but clang is still built. > >> is it possible >>>to build(world|kernel) && install(world|kernel) without the >>>clang toolchain? > > make -DWITHOUT_CLANG Good news! Thanks for taking the time to respond Eitan. --Chris > > > -- > Eitan Adler > ___ 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"
buildkernel error ...
hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ 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: buildkernel error ...
> hi all, > > I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 > > yesterday I have cvsup-ed src and was trying to buildkernel > bellow is error I receive: > --- [ cut ] > - > ... > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall > -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs > -fdiagnostics-show-option -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 > -fno-omit-frame-pointer > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror > /usr/src/sys/xdr/xdr_reference.c > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall > -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs > -fdiagnostics-show-option -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 > -fno-omit-frame-pointer > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror > /usr/src/sys/xdr/xdr_sizeof.c > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall > -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline > -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions > -Wmissing-include-dirs > -fdiagnostics-show-option -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 > -fno-omit-frame-pointer > -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror > /usr/src/sys/amd64/acpica/acpi_machdep.c > cc -c -x assembler-with-cpp -DLOCORE -O2 -frename-registers -pipe > -fno-strict-aliasing > -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign > -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option > -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 -fno-omit-frame-pointer -mcmodel=kernel > -mno-red-zone -mno-mmx > -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector > -Werror /usr/src/sys/amd64/acpica/acpi_switch.S > /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: > /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: > `xsetbv' > /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: > `xrstor (%rbx)' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/ZEUS_HOME. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > --- [ cut ] > - > > > nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF= replacing with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 > > -- > Zeus V. Panchenko jid:z...@im.ibs.dn.ua > IT Dpt., I.B.S. LLC GMT+2 (EET) > ___ > 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" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/lis
