Re: Problem building kernel STABLE12 amd64 arch
On Sun, Feb 17, 2019 at 09:11:46AM +, Filippo Moretti via freebsd-stable wrote: > I tried to update stable to yesterday build and I get the following error on > amd64 arch > linking kernel > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_legacy_intr) > > ld: error: undefined symbol: iflib_admin_intr_deferred > ... > Stop. > make: stopped in /usr/src > > Any help appreciatedsincerelyFilippo > It appears that your kernel configuration file -- unlike that of GENERIC -- does not include the entry: | # PCI/PCI-X/PCIe Ethernet NICs that use iflib infrastructure | device iflib This is pointed out in src/UPDATING: | 20190214: | Iflib is no longer unconditionally compiled into the kernel. Drivers | using iflib and statically compiled into the kernel, now require | the 'device iflib' config option. For the same drivers loaded as | modules on kernels not having 'device iflib', the iflib.ko module | is loaded automatically. A way to avoid the problem (and others of a similar nature) is to have your custom kernel configuration | include GENERIC and then customize from that point. Peace, david -- David H. Wolfskill da...@catwhisker.org There's a "national security emergency" all right -- at 1600 Pennsylvania Ave. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Problem building kernel STABLE12 amd64 arch
On Feb 17, 2019, at 4:11 AM, Filippo Moretti via freebsd-stable wrote: > I tried to update stable to yesterday build and I get the following error on > amd64 arch > linking kernel > ld: error: undefined symbol: iflib_get_softc referenced by if_vmx.c if_vmx.o:(vmxnet3_legacy_intr) > > ld: error: undefined symbol: iflib_admin_intr_deferred referenced by if_vmx.c if_vmx.o:(vmxnet3_legacy_intr) > > ld: error: undefined symbol: iflib_get_softc referenced by if_vmx.c if_vmx.o:(vmxnet3_tx_queues_alloc) > > ld: error: undefined symbol: iflib_dma_alloc_align referenced by if_vmx.c if_vmx.o:(vmxnet3_tx_queues_alloc) > ld: error: undefined symbol: iflib_get_softc referenced by if_vmx.c if_vmx.o:(vmxnet3_rx_queues_alloc) > > ld: error: undefined symbol: iflib_dma_alloc_align referenced by if_vmx.c if_vmx.o:(vmxnet3_rx_queues_alloc) > > ld: error: undefined symbol: iflib_get_softc referenced by if_vmx.c if_vmx.o:(vmxnet3_queues_free) > > ld: error: undefined symbol: iflib_dma_free referenced by if_vmx.c if_vmx.o:(vmxnet3_queues_free) > > ld: error: undefined symbol: iflib_get_dev referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre)>>> if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_sctx referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_softc_ctx referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_ifp referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_media referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_set_mac referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_pre) > ld: error: undefined symbol: iflib_get_softc_ctx referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_get_softc referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_dma_alloc_align referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_dma_alloc_align referenced by if_vmx.c if_vmx.o:(vmxnet3_attach_post) > > ld: error: too many errors emitted, stopping now (use -error-limit=0 to see > all errors) > *** Error code 1 > > Stop. > Stop. > make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING_VT > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > Any help appreciatedsincerelyFilippo Please see the 20190214 entry in /usr/src/UPDATING to fix this problem. Cheers, Paul. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problem building kernel STABLE12 amd64 arch
On Sun, Feb 17, 2019 at 09:11:46AM +, Filippo Moretti via freebsd-stable wrote: > I tried to update stable to yesterday build and I get the following error on > amd64 arch > linking kernel > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_legacy_intr) > > ld: error: undefined symbol: iflib_admin_intr_deferred > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_legacy_intr) > > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_tx_queues_alloc) > > ld: error: undefined symbol: iflib_dma_alloc_align > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_tx_queues_alloc) > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_rx_queues_alloc) > > ld: error: undefined symbol: iflib_dma_alloc_align > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_rx_queues_alloc) > > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_queues_free) > > ld: error: undefined symbol: iflib_dma_free > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_queues_free) > > ld: error: undefined symbol: iflib_get_dev > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre)>>> > >>>if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_sctx > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_softc_ctx > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_ifp > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_get_media > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre) > > ld: error: undefined symbol: iflib_set_mac > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_pre) > ld: error: undefined symbol: iflib_get_softc_ctx > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_get_softc > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_dma_alloc_align > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_post) > > ld: error: undefined symbol: iflib_dma_alloc_align > >>> referenced by if_vmx.c > >>> if_vmx.o:(vmxnet3_attach_post) > > ld: error: too many errors emitted, stopping now (use -error-limit=0 to see > all errors) > *** Error code 1 > > Stop. > Stop. > make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING_VT > *** Error code 1 > > Stop. > make[1]: stopped in /usr/src > *** Error code 1 > > Stop. > make: stopped in /usr/src > > Any help appreciatedsincerelyFilippo Read UPDATING note 20190214. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problem building kernel STABLE12 amd64 arch
I tried to update stable to yesterday build and I get the following error on amd64 arch linking kernel ld: error: undefined symbol: iflib_get_softc >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_legacy_intr) ld: error: undefined symbol: iflib_admin_intr_deferred >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_legacy_intr) ld: error: undefined symbol: iflib_get_softc >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_tx_queues_alloc) ld: error: undefined symbol: iflib_dma_alloc_align >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_tx_queues_alloc) ld: error: undefined symbol: iflib_get_softc >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_rx_queues_alloc) ld: error: undefined symbol: iflib_dma_alloc_align >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_rx_queues_alloc) ld: error: undefined symbol: iflib_get_softc >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_queues_free) ld: error: undefined symbol: iflib_dma_free >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_queues_free) ld: error: undefined symbol: iflib_get_dev >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre)>>> >>>if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_get_sctx >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_get_softc_ctx >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_get_ifp >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_get_media >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_set_mac >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_pre) ld: error: undefined symbol: iflib_get_softc_ctx >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_post) ld: error: undefined symbol: iflib_get_softc >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_post) ld: error: undefined symbol: iflib_dma_alloc_align >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_post) ld: error: undefined symbol: iflib_dma_alloc_align >>> referenced by if_vmx.c >>> if_vmx.o:(vmxnet3_attach_post) ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors) *** Error code 1 Stop. Stop. make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING_VT *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src Any help appreciatedsincerelyFilippo ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error building kernel on 10.3 (building ATH module)
Hi Yes the sources are from the DVD that I used to install the system. Then again I am trying to update the sources over svn but at some or the other point it just fails with a connection reset error even though I am on a pretty fast connection Is there an alternative? On Sun, Aug 20, 2017 at 12:47 PM, Aijaz Baig wrote: > I am getting an error while compiling the kernel. The log is as follows: > > -- > >>> stage 3.1: making dependencies > -- > > In file included from /usr/src/sys/modules/ath/../../dev/ath/if_ath.c:99: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > ^ > 1 error generated. > In file included from /usr/src/sys/modules/ath/../.. > /dev/ath/if_ath_debug.c:81: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > ^ > 1 error generated. > In file included from /usr/src/sys/modules/ath/../.. > /dev/ath/if_ath_keycache.c:76: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > > and a LOT of similar errors with the same 'ah_osdep.h' file not found > > ... > > then there is this as well: > > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_attach.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > ^ > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_beacon.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > ^ > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_interrupts.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > . > > I am unable to fathom how such an error would have escaped the developers > of this module (or am I missing something?) > > Secondly I commented out the entire WLAN section from within GENERIC but > for some reason it looks this module is still being compiled > > I am lost for directions. Please help > > > -- > > Best Regards, > Aijaz Baig > -- Best Regards, Aijaz Baig ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error building kernel on 10.3 (building ATH module)
On Sun, 20 Aug 2017 09:17:21 +0200, Aijaz Baig wrote: > > I am getting an error while compiling the kernel. The log is as follows: > > -- > >>> stage 3.1: making dependencies > -- > > In file included from /usr/src/sys/modules/ath/../../dev/ath/if_ath.c:99: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > ^ > 1 error generated. > In file included from > /usr/src/sys/modules/ath/../../dev/ath/if_ath_debug.c:81: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > ^ > 1 error generated. > In file included from > /usr/src/sys/modules/ath/../../dev/ath/if_ath_keycache.c:76: > In file included from @/dev/ath/if_athvar.h:40: > @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found > #include "ah_osdep.h" > > and a LOT of similar errors with the same 'ah_osdep.h' file not found > > ... > > then there is this as well: > > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_attach.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > ^ > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_beacon.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > ^ > 1 error generated. > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_interrupts.c:21:10: > fatal error: 'ah.h' file not found > #include "ah.h" > . > > I am unable to fathom how such an error would have escaped the developers > of this module (or am I missing something?) Probably the latter. Are you sure that your src tree is complete? Have you checked out your src tree with svn? What's the output of 'svn st' and 'svn info'? Have you tried with a clean /usr/obj? What commands do you use to build world/kernel? > Secondly I commented out the entire WLAN section from within GENERIC but > for some reason it looks this module is still being compiled To include/exclude modules from the build you have to set MODULES_OVERRIDE or WITHOUT_MODULES. This is explained in make.conf(5). -- Herbert ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Error building kernel on 10.3 (building ATH module)
I am getting an error while compiling the kernel. The log is as follows: -- >>> stage 3.1: making dependencies -- In file included from /usr/src/sys/modules/ath/../../dev/ath/if_ath.c:99: In file included from @/dev/ath/if_athvar.h:40: @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found #include "ah_osdep.h" ^ 1 error generated. In file included from /usr/src/sys/modules/ath/../../dev/ath/if_ath_debug.c:81: In file included from @/dev/ath/if_athvar.h:40: @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found #include "ah_osdep.h" ^ 1 error generated. In file included from /usr/src/sys/modules/ath/../../dev/ath/if_ath_keycache.c:76: In file included from @/dev/ath/if_athvar.h:40: @/dev/ath/ath_hal/ah.h:31:10: fatal error: 'ah_osdep.h' file not found #include "ah_osdep.h" and a LOT of similar errors with the same 'ah_osdep.h' file not found ... then there is this as well: 1 error generated. /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_attach.c:21:10: fatal error: 'ah.h' file not found #include "ah.h" ^ 1 error generated. /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_beacon.c:21:10: fatal error: 'ah.h' file not found #include "ah.h" ^ 1 error generated. /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar5210/ar5210_interrupts.c:21:10: fatal error: 'ah.h' file not found #include "ah.h" . I am unable to fathom how such an error would have escaped the developers of this module (or am I missing something?) Secondly I commented out the entire WLAN section from within GENERIC but for some reason it looks this module is still being compiled I am lost for directions. Please help -- Best Regards, Aijaz Baig ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
I use these options in my src.conf WITH_FAST_DEPEND=yes WITH_CCACHE_BUILD=yes I can often get build times of about 9 min but can got upto about 30 mins in jenkins depending on how much has changed. This is on a i5-3570K. It does have 32GB and ssd l2arc. Those times are for a buildworld, buildkernel packages for pkgbase. and j is set to 5 On 23 January 2017 at 18:09, Kevin Oberman wrote: > On Mon, Jan 23, 2017 at 6:10 AM, Lowell Gilbert < > freebsd-stable-lo...@be-well.ilk.org> wrote: > > > Walter Parker writes: > > > > > For decades there has always been a warning not to do parallel builds > of > > > the kernel or the world (Linux kernel builds also suggest not to do > > this). > > > > > > Every once in a while, I see people post about 5 minutes. This only > way I > > > can see this happening is by doing a parallel build (-j 16 on a Xeon > > > Monster box). > > > > > > Are parallel builds safe? If not, what are actual risk factors and can > > they > > > be mitigated? > > > > As a general rule, it's safe. But don't report failures from a > > parallel build. > > > > This is not so much an issue of parallel builds being unsupported > > as of the logs being harder to read. > > > Use of parallel builds of world and kernel are and have been supported > since at least 10.0. If a parallel build fails, the first step is usually > to do a single-job build. If it succeeds, there is a bug in the make > scripts that should be reported. If the single-job build also fails, a bug > should be reported with any errors included from the non-parallel build as > the parallel build makes the error context very difficult or even > impossible to determine from the log. > > Generally, I think the number of jobs should be slightly greater than the > number of available CPU threads. Back in 10.0 days I ran some tests that > showed the for 4 and 8 thread systems the improvements for large numbers of > jobs peaked at about CPU thread count + 2 and significantly larger numbers > of jobs caused a slight deterioration in performance. This was not true on > early hyper-threaded CPUs which did not effectively optimize > hyper-threading and things may have changed in the 6 or 7 years since I > tested and may be very different for systems with large numbers of threads > seen in servers today. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
On Mon, Jan 23, 2017 at 6:10 AM, Lowell Gilbert < freebsd-stable-lo...@be-well.ilk.org> wrote: > Walter Parker writes: > > > For decades there has always been a warning not to do parallel builds of > > the kernel or the world (Linux kernel builds also suggest not to do > this). > > > > Every once in a while, I see people post about 5 minutes. This only way I > > can see this happening is by doing a parallel build (-j 16 on a Xeon > > Monster box). > > > > Are parallel builds safe? If not, what are actual risk factors and can > they > > be mitigated? > > As a general rule, it's safe. But don't report failures from a > parallel build. > > This is not so much an issue of parallel builds being unsupported > as of the logs being harder to read. Use of parallel builds of world and kernel are and have been supported since at least 10.0. If a parallel build fails, the first step is usually to do a single-job build. If it succeeds, there is a bug in the make scripts that should be reported. If the single-job build also fails, a bug should be reported with any errors included from the non-parallel build as the parallel build makes the error context very difficult or even impossible to determine from the log. Generally, I think the number of jobs should be slightly greater than the number of available CPU threads. Back in 10.0 days I ran some tests that showed the for 4 and 8 thread systems the improvements for large numbers of jobs peaked at about CPU thread count + 2 and significantly larger numbers of jobs caused a slight deterioration in performance. This was not true on early hyper-threaded CPUs which did not effectively optimize hyper-threading and things may have changed in the 6 or 7 years since I tested and may be very different for systems with large numbers of threads seen in servers today. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
Walter Parker writes: > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). > > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). > > Are parallel builds safe? If not, what are actual risk factors and can they > be mitigated? As a general rule, it's safe. But don't report failures from a parallel build. This is not so much an issue of parallel builds being unsupported as of the logs being harder to read. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
On 23/01/2017 06:57, Walter Parker wrote: > Hi, > > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). > > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). > > Are parallel builds safe? If not, what are actual risk factors and can they > be mitigated? I remember warnings to the effect that while buildworld and buildkernel was safe, installworld and installkernel were not. I use -j32 on i7 monster boxes. -- J. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
On 23/01/2017 07:24, Sergei Akhmatdinov wrote: On Sun, 22 Jan 2017 22:57:46 -0800 Walter Parker wrote: For decades there has always been a warning not to do parallel builds of the kernel or the world (Linux kernel builds also suggest not to do this). Every once in a while, I see people post about 5 minutes. This only way I can see this happening is by doing a parallel build (-j 16 on a Xeon Monster box). Are parallel builds safe? If not, what are actual risk factors and can they be mitigated? Not only do I use -j, I also use ccache. Another option is to use WITH_META_MODE=YES, that's where most of the 5-minute reports come from, I imagine. I haven't used it myself. My kernel takes 10 minutes with world taking about two hours. I generally just leave them building overnight. The risks of parallel builds are mostly in the past, concurrency was still just coming out and there were chances that something would get compiled before it's dependency, breaking your compile and wasting all of those hours. Cheers, We always use -j for both kernel and world for years. While there's been a few niggles if the clock is out and its a rebuild they have been few and far between. Current cut down kernel build time is 1m and world build time is 22m here for FreeBSD 11.0-RELEASE on a dual E5-2640. Regards Steve ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Building Kernel and World with -j
On Sun, 22 Jan 2017 22:57:46 -0800 Walter Parker wrote: > For decades there has always been a warning not to do parallel builds of > the kernel or the world (Linux kernel builds also suggest not to do this). > > Every once in a while, I see people post about 5 minutes. This only way I > can see this happening is by doing a parallel build (-j 16 on a Xeon > Monster box). > > Are parallel builds safe? If not, what are actual risk factors and can they > be mitigated? Not only do I use -j, I also use ccache. Another option is to use WITH_META_MODE=YES, that's where most of the 5-minute reports come from, I imagine. I haven't used it myself. My kernel takes 10 minutes with world taking about two hours. I generally just leave them building overnight. The risks of parallel builds are mostly in the past, concurrency was still just coming out and there were chances that something would get compiled before it's dependency, breaking your compile and wasting all of those hours. Cheers, -- Sergei Akhmatdinov My GPG public key: gpg --keyserver pgp.mit.edu --recv-keys AD800D99 pgpGLxb_q_7JW.pgp Description: OpenPGP digital signature
Building Kernel and World with -j
Hi, For decades there has always been a warning not to do parallel builds of the kernel or the world (Linux kernel builds also suggest not to do this). Every once in a while, I see people post about 5 minutes. This only way I can see this happening is by doing a parallel build (-j 16 on a Xeon Monster box). Are parallel builds safe? If not, what are actual risk factors and can they be mitigated? Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Possible issue building kernel modules: dialog4ports invocation
This morning, my laptop & build machine (daily) source-based updates
for stable/11 were uneventful, but the (weekly) update to my desktop
at work died (temporarily) during an attempt to build a kernel
module (because I have
PORTS_MODULES=x11/nvidia-driver
in etcsrc.conf):
...
--- kernel.full ---
linking kernel.full
ctfmerge -L VERSION -g -o kernel.full ...
text data bssdec hex filename
22011101 1257388 4963232 28231721 0x1aec829 kernel.full
--- kernel.debug ---
objcopy --only-keep-debug kernel.full kernel.debug
--- kernel ---
objcopy --strip-debug --add-gnu-debuglink=kernel.debug kernel.full kernel
--- all ---
===> Ports module x11/nvidia-driver (all)
cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP PATH=/
usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj
/usr/src/tmp/legacy/bin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/b
in:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/s
rc OSVERSION=1100507 WRKDIRPREFIX=/usr/obj/usr/src/sys/ /usr/obj/usr/src/make.
amd64/bmake -B clean all
===> Cleaning for nvidia-driver-367.44_3
*** [all] Stopped -- signal 22
Running "ps" showed that a few processes (including dialog4ports)
had received SIGSTOP; sending them a SIGCONT wasn't helpful (as in
"didn't seem to cause the processes to resume execution").
I finally did circumvent the issue by (separately) running "portmaster
x11/nvidia-driver", which brought up the dialog4ports menu Just Fine,
then built & installed the port.
After having done that, build kernel (including updating the
x11/nvidia-driver module again), install kernel, install world (as
well as mergemaster &c.) all worked.
In case it's relevant, I ran the build within script(1), running
in a tmux(1) session.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Epistemology for post-truthers: How do we select parts of reality to ignore?
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
Error building kernel in 9.0-BETA3: use of uninitialized variable in ipfw
Just tried to build a new kernel in 9.0-BETA3 with the IPFIREWALL option, and found that the build halts with a compiler error. The error occurs at netinet/ipfw/ip_fw_pfil.c, line 185, where the compiler complains that the variable "len" is used before intialization. Problem occurs on both i386 and amd64 platforms. Sample kernel config follows: cpu HAMMER ident BETA #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking #optionsINET6 # IPv6 communications protocols #optionsSCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support #optionsUFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #optionsUFS_GJOURNAL# Enable gjournal-based UFS journaling #optionsMD_ROOT # MD is a potential root device #optionsNFSCL # New Network Filesystem Client #optionsNFSD# New Network Filesystem Server #optionsNFSLOCKD# Network Lock Manager #optionsNFS_ROOT# NFS usable as /, requires NFSCL #optionsMSDOSFS # MSDOS Filesystem #optionsCD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization #optionsCOMPAT_FREEBSD32# Compatible with i386 binaries #optionsCOMPAT_FREEBSD4 # Compatible with FreeBSD4 #optionsCOMPAT_FREEBSD5 # Compatible with FreeBSD5 #optionsCOMPAT_FREEBSD6 # Compatible with FreeBSD6 #optionsCOMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI #optionsKTRACE # ktrace(1) support #optionsSTACK # 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 #optionsHWPMC_HOOKS # Necessary kernel hooks for hwpmc(4) #optionsAUDIT # Security event auditing #optionsMAC # TrustedBSD MAC Framework ##options KDTRACE_FRAME # Ensure frames are compiled in ##options KDTRACE_HOOKS # Kernel DTrace hooks #optionsINCLUDE_CONFIG_FILE # Include this file in kernel # Debugging for use in -current #optionsKDB # Enable kernel debugger support. #optionsDDB # Support DDB. #optionsGDB # Support remote GDB. #optionsDEADLKRES # Enable the deadlock resolver #optionsINVARIANTS # Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT # Extra sanity checks of internal structures, required by IN VARIANTS #optionsWITNESS # Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for speed #optionsMALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi device pci # Floppy drives #device fdc # ATA controllers device ahci# AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers options ATA_CAM # Handle legacy controllers with CAM options ATA_STATIC_ID # Static device numbering #device mvs # Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA #device siis# SiliconImage SiI3124/SiI3132/SiI3531 SATA # SCSI Controllers #device ahc # AHA2940 and onboard AIC7xxx devices #optionsAHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. #
Re: compile error while building kernel
On 3/28/08, walt <[EMAIL PROTECTED]> wrote: > Rance Hall wrote: > > >> cc -c -O -pipe -march=athlon-xp -std=c99 -g -Wall -Wredundant-decls > > > cc -c -o -pipe -march=athlon-mp -std=c99 -g -Wall -Wredundant-decls > > ^^ > > Did you type an 'o' instead of an 'O' for your optimization flag in > make.conf? Right, my make.conf was wrong, because of the way it was wrong it only affects kernel builds, I have fixed the problem, and everything seems to be fine. Thanks all for your help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
Rance Hall wrote: cc -c -O -pipe -march=athlon-xp -std=c99 -g -Wall -Wredundant-decls > cc -c -o -pipe -march=athlon-mp -std=c99 -g -Wall -Wredundant-decls ^^ Did you type an 'o' instead of an 'O' for your optimization flag in make.conf? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
On Thu, Mar 27, 2008 at 09:19:24PM -0500, Rance Hall wrote: > [/usr/src/sys/i386/compile/GENERIC] [EMAIL PROTECTED] make > cc -c -o -pipe -march=athlon-mp -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../../.. -I../../../contrib/altq > -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h > -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 ../../../i386/i386/genassym.c > NM='nm' sh ../../../kern/genassym.sh genassym.o > assym.s > nm: 'genassym.o': No such file I see the problem. Look closely there at the cc line: cc -c -o -pipe ... genassym.c There is no object destination specified via -o. This is why no .o file is being created. What I'd like to know is why gcc isn't complaining about arguments being incorrect. It should be: cc -c -pipe ... genassym.c Are you sure you aren't setting something in make.conf pertaining to optimisations, up, using lowercase -o instead of capital -O ? This would cause what you're seeing. Look closely at walt's cc line and you'll see what I mean: [EMAIL PROTECTED]/usr/src/sys/i386/compile/GENERIC #make cc -c ... -O ... ../../../i386/i386/genassym.c -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
On Thu, Mar 27, 2008 at 8:16 PM, walt <[EMAIL PROTECTED]> wrote: > > Hm. Well, I just compiled GENERIC using the 'old' method. Your missing > symbols are defined in assym.s, which is generated during the compile by > genassym.sh right at the beginning: > > [EMAIL PROTECTED]/usr/src/sys/i386/compile/GENERIC #make > cc -c -O -pipe -march=athlon-xp -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../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -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 > ../../../i386/i386/genassym.c > NM='nm' sh ../../../kern/genassym.sh genassym.o > assym.s > > Do you see something different at your end? > I never noticed before but since you have mentioned that the values are supposed to be set in assym.s in the step right before my failure I went back and looked and I get this: [/usr/src/sys/i386/compile/GENERIC] [EMAIL PROTECTED] make cc -c -o -pipe -march=athlon-mp -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../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -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 ../../../i386/i386/genassym.c NM='nm' sh ../../../kern/genassym.sh genassym.o > assym.s nm: 'genassym.o': No such file which must be the problem. If there is no genassym.o file then assym.s doesnt get created. Then when assym.s doesnt get created the rest of the build will fail miserably ok, so I know what the problem is. Wonder what to do about it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
On Thu, 27 Mar 2008, Rance Hall wrote: > On 3/27/08, walt <[EMAIL PROTECTED]> wrote: > > > > You might try searching your source tree for .depend and .o files and > > delete any you find. Also, you could try building the old way: > > > > #cd /usr/src/sys/i386/conf > > #config GENERIC > > #cd ../compile/GENERIC > > #make all install > > > > If that works then you must have some funny files in your source tree > > that don't belong there. > > > searched for *.depend and *.o files, (none found) used find /usr/src > -name "*.depend" -print to get a list of files that needed to be > deleted. > > then tried the compile the old way as suggested, that fails too, with > the same errors and same files. Hm. Well, I just compiled GENERIC using the 'old' method. Your missing symbols are defined in assym.s, which is generated during the compile by genassym.sh right at the beginning: [EMAIL PROTECTED]/usr/src/sys/i386/compile/GENERIC #make cc -c -O -pipe -march=athlon-xp -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../../.. -I../../../contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -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 ../../../i386/i386/genassym.c NM='nm' sh ../../../kern/genassym.sh genassym.o > assym.s Do you see something different at your end? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
On 3/27/08, walt <[EMAIL PROTECTED]> wrote: > > You might try searching your source tree for .depend and .o files and > delete any you find. Also, you could try building the old way: > > #cd /usr/src/sys/i386/conf > #config GENERIC > #cd ../compile/GENERIC > #make all install > > If that works then you must have some funny files in your source tree > that don't belong there. searched for *.depend and *.o files, (none found) used find /usr/src -name "*.depend" -print to get a list of files that needed to be deleted. then tried the compile the old way as suggested, that fails to, with the same errors and same files. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
Rance Hall wrote: On Wed, Mar 26, 2008 at 8:48 PM, Rance Hall<[EMAIL PROTECTED]> wrote: On Wed, Mar 26, 2008 at 7:32 PM, walt<[EMAIL PROTECTED]> wrote: > Rance Hall wrote: >> ... > > > im running an amd athlon64 processor but the i386 code. > > > > my march is athlon-mp (the system translates my athlon64 > > automatically to this in i386 mode)... > > ... > Anyway, if your make.conf defines CPUTYPE or MACHINE_ARCH as > athlon64 just try changing it to K8 or athlon-mp or athlon and > see if anything changes. > I tried setting CPUTYPE=athlon-mp in make.conf and I still couldn't buiild a kernel. You might try searching your source tree for .depend and .o files and delete any you find. Also, you could try building the old way: #cd /usr/src/sys/i386/conf #config GENERIC #cd ../compile/GENERIC #make all install If that works then you must have some funny files in your source tree that don't belong there. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
On Wed, Mar 26, 2008 at 8:48 PM, Rance Hall <[EMAIL PROTECTED]> wrote: > On Wed, Mar 26, 2008 at 7:32 PM, walt <[EMAIL PROTECTED]> wrote: > > Rance Hall wrote: > > > ... > > > > > im running an amd athlon64 processor but the i386 code. > > > > > > my march is athlon-mp (the system translates my athlon64 > > > automatically to this in i386 mode)... > > > > I've been too cheap to buy a 64-bit machine, so obviously I'm > > making a blind guess here :o) but the words above make me uneasy. > > > > If you're running 32-bit code, then your make.conf should not be > > using 'athlon64' at all and thus it should not need translation, > > right? (I'm truly asking, not lecturing.) > > > > Anyway, if your make.conf defines CPUTYPE or MACHINE_ARCH as > > athlon64 just try changing it to K8 or athlon-mp or athlon and > > see if anything changes. > > > > I tried setting CPUTYPE=athlon-mp in make.conf and I still couldn't > buiild a kernel. > > It seems something else is happening, but I sure dont know what it is. > nor why no one else has reported this problem yet. > I tried setting CPUTYPE=athlon-mp in make.conf and I still couldn't buiild a kernel. It seems something else is happening, but I sure dont know what it is. nor why no one else has reported this problem yet. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: compile error while building kernel
Rance Hall wrote: > ... im running an amd athlon64 processor but the i386 code. my march is athlon-mp (the system translates my athlon64 automatically to this in i386 mode)... I've been too cheap to buy a 64-bit machine, so obviously I'm making a blind guess here :o) but the words above make me uneasy. If you're running 32-bit code, then your make.conf should not be using 'athlon64' at all and thus it should not need translation, right? (I'm truly asking, not lecturing.) Anyway, if your make.conf defines CPUTYPE or MACHINE_ARCH as athlon64 just try changing it to K8 or athlon-mp or athlon and see if anything changes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
compile error while building kernel
On a test box I upgraded from 7.0-RELEASE to -STABLE buildworld works fine, but buildkernel KERNCONF=GENERIC fails with two fatal errors. /usr/src/sys/i386/i386/locore.s:905:5: error: "KERNLOAD" is not defined /usr/src/sys/i386/i386/locore.s:905:22: error: "PDRSHIFT" is not defined I can't find any reference to this either in the list archives or in UPDATING. im running an amd athlon64 processor but the i386 code. my march is athlon-mp (the system translates my athlon64 automatically to this in i386 mode) I will be happy to provide other details like make.conf if needed. I just cant find any docs about what these to vars are supposed to be/do so I could just set the values to something myself. hints appreciated. last cvsup yesterday 3/25 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFLAGS vs COPTFLAGS for building kernel modules
/usr/share/examples/etc/make.conf v1.265.2.1 states: # To compile just the kernel with special optimizations, you should use # this instead of CFLAGS (which is not applicable to kernel builds anyway). # There is very little to gain by using higher optimization levels, and doing # so can cause problems. # #COPTFLAGS= -O -pipe Unfortunately, it seems that kernel modules are build with CFLAGS rather than COPTFLAGS. This is somewhat embarrassing when CFLAGS includes options that don't work in the kernel but aren't explicitly disabled (eg -msse3). My make-foo isn't up to quickly isolating the problem. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building kernel, -mno-3dnow and stuff.
From: "Darren Pilgrim" cc -O -pipe -march=pentiumpro -march=athlon-tbird -I/<...cut...> -mno-mmx -mno-3dnow -mno-sse -mno-sse2 These are disabled because they cause problems when used in the kernel. my ``/etc/make.conf'' file: - CPUTYPE=athlon-tbird CFLAGS= -O -pipe -march=pentiumpro COPTFLAGS= -O -fomit-frame-pointer -march=pentiumpro -pipe - You should not put -march in your FLAGS variables. CPUTYPE determines the correct architecture- and processor-specific compiler flags. Thanks a lot. Now it's clear to me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Building kernel, -mno-3dnow and stuff.
From: Viatcheslav Fedorov > > cc -O -pipe -march=pentiumpro -march=athlon-tbird > -I/<...cut...> -mno-mmx -mno-3dnow -mno-sse -mno-sse2 These are disabled because they cause problems when used in the kernel. > my ``/etc/make.conf'' file: > - > CPUTYPE=athlon-tbird > CFLAGS= -O -pipe -march=pentiumpro > COPTFLAGS= -O -fomit-frame-pointer -march=pentiumpro -pipe > - You should not put -march in your FLAGS variables. CPUTYPE determines the correct architecture- and processor-specific compiler flags. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Building kernel, -mno-3dnow and stuff.
Hello. I've recently CVSupped from 5.3-RELEASE to 5.4-STABLE when I ``make buildkernel'' I get the output like this: cc -O -pipe -march=pentiumpro -march=athlon-tbird -I/<...cut...> -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sys/modules/acpi/acpi/../../../contrib/dev/acpica/dsfield.c (It compiles OK, but those -mno-* ?!?!) my ``/etc/make.conf'' file: - CPUTYPE=athlon-tbird CFLAGS= -O -pipe -march=pentiumpro COPTFLAGS= -O -fomit-frame-pointer -march=pentiumpro -pipe NOPROFILE=true NO_BIND=true DOC_LANG=en_US.ISO8859-1 ru_RU.KOI8-R - So, what did I do wrong? Why on my athlon-tbird 1200Mhz it compiles with -mno-3dnow ? I guess it's the error in make.conf, but where? Thanks in advance, Viatcheslav ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bug ? Building kernel/world error on Cyrix
Thats the official name of the Cyrix, although they were far from being
actual 686 CPUs. The clock speed reported is also correct. Cyrix rated
them with a PR rating which, unlike the Athlon XP ratings, was overly
optimistic. Your "200MHz" is a 200PR CPU, which did run at 166MHz, but
had the performance of maybe a 133 Pentium (I had a 166PR, which ran at
133, until it self destructed). I would try changing CPUTYPE to i586 or
i486.
All of this doesn't explain the perl related error you're seeing though
:) Try recvsuping.
Yann
Guilherme Oliveira wrote:
>Hi !
>
>I'm having serious problems building kernel or world in my Cyrix 200MHZ.
>
>Booting '4.5-RELEASE #0' it detects my processor as being Cyrix 6x86MX
>(167.05-MHz 686-class CPU), that I think it's wrong ('6x86' ?!?!) and
>maybe this is the origin for all my problems.
>
>I've cvsup'd and builded freebsd all the time without problem until +-
>4.5 RELEASE.
>I've tried building GENERIC with the same result.
>
>I have tried building world+kernel with 'CPUTYPE=i686' in make.conf and
>'cpu I686_CPU' (as allways did) in kernel but it gives me error in:
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Bug ? Building kernel/world error on Cyrix
Hi !
I'm having serious problems building kernel or world in my Cyrix 200MHZ.
Booting '4.5-RELEASE #0' it detects my processor as being Cyrix 6x86MX
(167.05-MHz 686-class CPU), that I think it's wrong ('6x86' ?!?!) and
maybe this is the origin for all my problems.
I've cvsup'd and builded freebsd all the time without problem until +-
4.5 RELEASE.
I've tried building GENERIC with the same result.
I have tried building world+kernel with 'CPUTYPE=i686' in make.conf and
'cpu I686_CPU' (as allways did) in kernel but it gives me error in:
===> portal
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
perl @/kern/vnode_if.pl -h @/kern/vnode_if.src
Internal error at @/kern/vnode_if.pl line 248, chunk 472.
*** Error code 255
Stop in /usr/src/sys/modules/portal.
*** Error code 1
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/obj/usr/src/sys/SARPA.
*** Error code 1
Stop in /usr/src.
*** Error code 1
I have tried building world+kernel with 'CPUTYPE=i586' in make.conf and
'cpu I586_CPU' in kernel but it gives me error in:
/obj/usr/src/i386/usr/include -c /usr/src/bin/sh/error.c
cc -O -pipe -march=pentium -DSHELL -I. -I/usr/src/bin/sh -Wall
-Wformat -I/usr
/obj/usr/src/i386/usr/include -c /usr/src/bin/sh/eval.c
{standard input}: cc: Assembler messages:
Internal compiler error: program cc1 got fatal signal 11{standard
input}:0:
Warning: *** Error code 1
end of file not at end of a line; newline inserted
Stop in /usr/src/bin/sh.
*** Error code 1
Stop in /usr/src/bin.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
bash-2.05# {standard input}:1107: Error: unbalanced parenthesis in
operand 2.
My partially dmesg:
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
reserved.
FreeBSD 4.5-RELEASE #0: Mon Feb 11 05:52:10 WET 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SARPA
Timecounter "i8254" frequency 1193182 Hz
CPU: Cyrix 6x86MX (167.05-MHz 686-class CPU)
Origin = "CyrixInstead" Id = 0x600 Stepping = 0 DIR=0x0452
Features=0x80a135
real memory = 134217728 (131072K bytes)
avail memory = 127442944 (124456K bytes)
Preloaded elf kernel "kernel" at 0xc0327000.
md0: Malloc disk
Using $PIR table, 5 entries at 0xc00fdb80
apm0: on motherboard
apm: found APM BIOS v1.2, connected at v1.2
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
pcib1: at device 1.0 on
pci0
pci1: on pcib1
pci1: at 5.0 irq 11
isab0: at device 7.0 on pci0
isa0: on isab0
atapci0: port 0xe000-0xe00f at device 7.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: port 0xe400-0xe41f irq 10 at device
7.2 on pci0
usb0: on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
chip1: at device 7.3 on pci0
My kernel configuration:
#
# GENERIC -- Generic kernel configuration file for FreeBSD/i386
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
#http://www.FreeBSD.org/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 ./LINT configuration file. If you
are
# in doubt as to the purpose or necessity of a line, check first in
LINT.
#
# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.35 2001/09/27 17:43:06
alfred Exp $
machine i386
cpu I586_CPU# aka Pentium Pro(tm)
ident SARPA
maxusers0
options MATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep
this!]
options SOFTUPDATES #Enable FFS soft updates support
options UFS_DIRHASH
options MSDOSFS #MSDOS Filesystem
options NTFS#NT File System
options CD9660 #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root, CD9660
required
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP
THIS!]
options UCONSOLE#Allow users to grab the console
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
Re: building kernel problem w/ linux_proto.h
On Sunday 06 January 2002 10:28 am, parv wrote: > hi, > > i cvsup'd old sources (4-stable oct 13 2001) to current (4-stable > 2002.01.05.15.45.19). at this point i am stuck at errors w/ > linux_proto.h -- which had been reported at least since nov. 2001 > to this month. > > first i ran make cleandir in /usr/src, removed /usr/obj/*, and tried > to build kernel. after first snag, i searched the internet which > indicated to read src/UPDATING. > > well, first i did "make modules-clean" in > src/sys/compile/$KERNCONF as i do not have MODULES_WITH_WORLD=yes in > /etc/make.conf. after that when i tried again, it failed. so i > tried again after running "make cleandir" in src/sys/modules/linux > w/o any success. > > at this point would above two steps help if i revert to earlier > sources, and then back to current -stable? any other pointers? This is probably a more subtle fix than this, but the following is what finally worked for me: rm -r /usr/obj rm -r /usr/src cvsup /root/sup/conf ln -s /root/BTS /usr/src/sys/i386/conf CAUTION1: This wipes out your kernel configuration. I keep mine in /root all the time (I back up /root but not /usr/src), so I could just re-link it after the wipe (my kernel config is called BTS). If you don't, stuff it away someplace safe. CAUTION2: Without a broadband, this would be tiresome--it causes the entire source to be re-downloaded from the net. NOTE: There is almost certainly a more subtle solution. But if you have a fast connection, just doing the above is probably a lot easier & less frustrating than tracking it down. -- Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work) Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) http://www.babbleon.org ---> Free Dmitry Sklyarov! (let him go home) <--- http://www.eff.org http://www.programming-freedom.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: building kernel problem w/ linux_proto.h
The UPDATING instructions also didn't work for me, though I did this over a month ago. I seem to recall that rm -rf /usr/src/sys/modules/linux /usr/src/sys/compat/linux followed by a cvsup; make buildworld && make buildkernel got things going again. A bit of a sledgehammer, I admit. jay parv wrote: > in message <[EMAIL PROTECTED]>, > wrote M. Warner Losh thusly... > >>In message: <[EMAIL PROTECTED]> >>parv <[EMAIL PROTECTED]> writes: >> > ... > >>: well, first i did "make modules-clean" in src/sys/compile/$KERNCONF >>: as i do not have MODULES_WITH_WORLD=yes in /etc/make.conf. after >>: that when i tried again, it failed. so i tried again after running >>: "make cleandir" in src/sys/modules/linux w/o any success. >> >>If you are building the kernel by hand, try rm -rf modules in >>src/sys/compile/$KERNCONF. >> > > yes, sometimes i build kernel by hand; and since 4-stable, i build > kernel w/ world every time via KERNCONF. > > i did try that; didn't work. then i tried after obliterating the > src/sys/compile/$KERNCONF, that didn't work either. unless, > somebody has any other option, i will try w/ clean cvsup'd "src" > tree. > > before i do that, is there anything else that i could do manually? > > - parv > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: building kernel problem w/ linux_proto.h
in message <[EMAIL PROTECTED]>, wrote Brian T. Schellenberger thusly... > > On Sunday 06 January 2002 10:28 am, parv wrote: > > hi, > > > > i cvsup'd old sources (4-stable oct 13 2001) to current (4-stable > > 2002.01.05.15.45.19). at this point i am stuck at errors w/ > > linux_proto.h ... > > first i ran make cleandir in /usr/src, removed /usr/obj/*, and tried > > to build kernel. after first snag, i searched the internet which > > indicated to read src/UPDATING. > > > > well, first i did "make modules-clean" in > > src/sys/compile/$KERNCONF as i do not have MODULES_WITH_WORLD=yes in > > /etc/make.conf. after that when i tried again, it failed. so i > > tried again after running "make cleandir" in src/sys/modules/linux > > w/o any success. > > This is probably a more subtle fix than this, but the following is what > finally worked for me: > > rm -r /usr/obj > rm -r /usr/src > cvsup /root/sup/conf > ln -s /root/BTS /usr/src/sys/i386/conf ... > CAUTION2: Without a broadband, this would be tiresome--it causes the entire > source to be re-downloaded from the net. you know what, that's exactly what i am doing right now... it started at 2.43p edt, and currently cvsup is downloading src/contrib/ncurses; time now is 6.23p. a long way to go on dial up connection. > NOTE: There is almost certainly a more subtle solution. But if you have a > fast connection, just doing the above is probably a lot easier & less > frustrating than tracking it down. i would sure hope that somebody else will track it down, as doing fresh cvsup of src tree needs patience, at least on dial up connection. thanks brian. - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problems with building kernel in 4.3-STABLE cvsuped 15 min ago
Then `make cleandir' twice in sys/modules/ipfilter to get rid of stale .depend files. Then `make obj; make depend; make all' from there once again. Everything should be OK now. On Fri, Jun 15, 2001 at 10:34:48AM +0200, Gunnar Flygt wrote: > On Fri, Jun 15, 2001 at 11:30:36AM +0300, Ruslan Ermilov wrote: > > Check that you have this: > > > > $FreeBSD: src/sys/modules/ipfilter/Makefile,v 1.2.2.2 2001/06/07 05:11:44 jlemon >Exp $ > > > > Geee, real quick answer there! :) This is what I've got: > 2$ less /usr/src/sys/modules/ipfilter/Makefile > # $FreeBSD: src/sys/modules/ipfilter/Makefile,v 1.2.2.2 2001/06/07 05:11:44 jlem > on Exp $ > > So it seems OK. I found the file under src/sys/contrib/ipfilter/netinet > instead. Did a dirty solution and linked it to the directory wanted in > the Makefile. Will it work? > > > On Fri, Jun 15, 2001 at 10:28:08AM +0200, Gunnar Flygt wrote: > > > Is anyone having trouble building GENERIC as of today? It stops when > > > trying to build module ipfilter. Looks like this: > > > > > > ===> ipfilter > > > make: don't know how to make /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ip > > > l.c. Stop > > > *** Error code 2 > > > > -- > > Ruslan Ermilov Oracle Developer/DBA, > > [EMAIL PROTECTED] Sunbay Software AG, > > [EMAIL PROTECTED] FreeBSD committer, > > +380.652.512.251Simferopol, Ukraine > > > > http://www.FreeBSD.org The Power To Serve > > http://www.oracle.com Enabling The Information Age > > -- >__o > regards, Gunnar ---_ \<,_ > email: [EMAIL PROTECTED] (_)/ (_) -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problems with building kernel in 4.3-STABLE cvsuped 15 min ago
On Fri, Jun 15, 2001 at 11:30:36AM +0300, Ruslan Ermilov wrote: > Check that you have this: > > $FreeBSD: src/sys/modules/ipfilter/Makefile,v 1.2.2.2 2001/06/07 05:11:44 jlemon Exp >$ > Geee, real quick answer there! :) This is what I've got: 2$ less /usr/src/sys/modules/ipfilter/Makefile # $FreeBSD: src/sys/modules/ipfilter/Makefile,v 1.2.2.2 2001/06/07 05:11:44 jlem on Exp $ So it seems OK. I found the file under src/sys/contrib/ipfilter/netinet instead. Did a dirty solution and linked it to the directory wanted in the Makefile. Will it work? > On Fri, Jun 15, 2001 at 10:28:08AM +0200, Gunnar Flygt wrote: > > Is anyone having trouble building GENERIC as of today? It stops when > > trying to build module ipfilter. Looks like this: > > > > ===> ipfilter > > make: don't know how to make /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ip > > l.c. Stop > > *** Error code 2 > > -- > Ruslan ErmilovOracle Developer/DBA, > [EMAIL PROTECTED] Sunbay Software AG, > [EMAIL PROTECTED]FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.orgThe Power To Serve > http://www.oracle.com Enabling The Information Age -- __o regards, Gunnar ---_ \<,_ email: [EMAIL PROTECTED] (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problems with building kernel in 4.3-STABLE cvsuped 15 min ago
Check that you have this: $FreeBSD: src/sys/modules/ipfilter/Makefile,v 1.2.2.2 2001/06/07 05:11:44 jlemon Exp $ On Fri, Jun 15, 2001 at 10:28:08AM +0200, Gunnar Flygt wrote: > Is anyone having trouble building GENERIC as of today? It stops when > trying to build module ipfilter. Looks like this: > > ===> ipfilter > make: don't know how to make /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ip > l.c. Stop > *** Error code 2 -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Problems with building kernel in 4.3-STABLE cvsuped 15 min ago
Is anyone having trouble building GENERIC as of today? It stops when trying to build module ipfilter. Looks like this: ===> ip6fw cc -nostdinc -O -pipe -DIPV6FIREWALL -D_KERNEL -Wall -Wredundant-decls -Wnest ed-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -W cast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../ include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/ip6fw/../../netine t6/ip6_fw.c ld -r -o ip6fw.kld ip6_fw.o gensetdefs ip6fw.kld cc -nostdinc -O -pipe -DIPV6FIREWALL -D_KERNEL -Wall -Wredundant-decls -Wnest ed-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -W cast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../ include -mpreferred-stack-boundary=2 -c setdef0.c cc -nostdinc -O -pipe -DIPV6FIREWALL -D_KERNEL -Wall -Wredundant-decls -Wnest ed-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -W cast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../ include -mpreferred-stack-boundary=2 -c setdef1.c ld -Bshareable -o ip6fw.ko setdef0.o ip6fw.kld setdef1.o ===> ipfilter make: don't know how to make /usr/src/sys/modules/ipfilter/../../netinet/mlfk_ip l.c. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** 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. It seems there is no mlfk_ipl.c in the directory desired. -- __o regards, Gunnar ---_ \<,_ email: [EMAIL PROTECTED] (_)/ (_) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem building kernel
/usr/src/usr.bin/xinstall for the sources, and /usr/obj/usr/src/usr.bin/xinstall for the .o and executable. The "x" had to be added before the name to avoid confusion with make targets: for example, if somebody runs "make install" from /usr/src/usr.bin/xinstall, do they want to install install(1), or do they simply want to compile it? Eric On Thu, Jul 20, 2000 at 11:58:25PM -0500, Stephen Montgomery-Smith wrote: > I had a problem with install a few days ago, and a similar cure would > have helped me immensely. But I don't have /usr/src/usr.bin/install > in my sources. Where are the sources for install actually kept? > After a make buildworld, where is the binary kept in the /usr/obj tree? > I looked for ages, and simply could not find them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
building kernel
cvsuped a few hours ago RELENG_4: root@vic# cd /usr/src/sys/i386/conf root@vic# config -r Laa Removing old directory ../../compile/Laa: Done. Don't forget to do a ``make depend'' Kernel build directory is ../../compile/Laa root@vic# cd ../../compile/Laa root@vic# make depend all install : ... -mpreferred-stack-boundary=2 setdef1.c touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c sh ../../conf/newvers.sh LAA cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel vpo.o: In function `vpo_attach': vpo.o(.text+0xcf): undefined reference to `cam_simq_alloc' vpo.o(.text+0x100): undefined reference to `cam_sim_alloc' vpo.o(.text+0x110): undefined reference to `cam_simq_free' vpo.o(.text+0x11e): undefined reference to `xpt_bus_register' vpo.o(.text+0x13a): undefined reference to `xpt_create_path' vpo.o(.text+0x153): undefined reference to `xpt_bus_deregister' vpo.o(.text+0x15d): undefined reference to `cam_sim_free' vpo.o: In function `vpo_action': vpo.o(.text+0x459): undefined reference to `xpt_done' vpo.o(.text+0x469): undefined reference to `xpt_ Stop in /usr/src/sys/compile/Laa. root@vic# -- Laa. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
