Re: odd message from ld in -current around 9.0 branchpoint
On Tue, 2014-04-29 at 13:41 +0800, Julian Elischer wrote: I'm trying to compile a system based on current from just before the 9.x branchpoint. during hte build I got the following message: /usr/bin/ld: this linker was not configured to use sysroots does anyone have any idea what this means in a broader context? did I misconfigure something when I built this system? Julian Are you using ccache? I vaguely remember some reports of this in the past, and I think it was caused by using a version of ccache that wasn't compatible with clang, or something along those lines. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Make variables to force non default libraries and includes?
On Tue, 2014-04-29 at 13:31 +0800, Julian Elischer wrote:
On 4/29/14, 8:57 AM, Ian Lepore wrote:
On Mon, 2014-04-28 at 18:36 -0600, Warner Losh wrote:
On Apr 28, 2014, at 1:48 AM, Julian Elischer jul...@freebsd.org wrote:
I need to do the equivalent of cd /usr/src/cddl/usr.sbin/dtrace; make
DESTDIR=/mumble all install”
cd /usr/src
make distributeworld DESTDIR=/mumble
cd cddl/usr.sbin/dtrace
make buildenv
make all install
but it pulls in libraries from the base system, which differ slightly
from those in the source tree.
The above will create the right /mumble hierarchy, and will pull the
libraries from the build rather than the local system.
How can I force it to use /mumble2/include and /mumble2/lib instead of / ?
I can pre-populate /mumble2 using make buildworld, make libraries,
and make includes but
I need to be able to do selective builds of just subdirectories after
that.. I haven't spotted the right way of forcing the use of the
--system_root /mumble2 option in the compiles.
I know we do it in 'buildworld' is there a more generic way?
I have been looking in the .mk files but I haven't spotted it so far.
You’re asking for some serious split-brain action. chroot builds are
likely your best option. There’s no easy way to force this, although you
might get some milage out of WMAKEENV options, but I think we bake most of
the where to look for things options into the binaries. One crazy option
would be to set CC=“cc —sysroot /mumble” but I’m sure there be dragons
there…
Good luck with this crazy, never have we supported it very well, option :)
Warner
Actually the hooks are in place to do this stuff. Instead of make
buildenv to get an interactive shell you can do something like
BLDENV=`${MAKE} buildenvvars`
chroot buildchroot/ env -i $${BLDENV} cd /usr/src/somewhere \
make all install
-- Ian
Is there a way to specify a different toolchain destination? i.e. not
/usr/obj/usr/src/tmp ?
Not right now -- all that stuff is in Makefile.inc1 (WORLDTMP var and
related stuff) and there are no provisions for overriding it.
-- Ian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: odd message from ld in -current around 9.0 branchpoint
On 4/29/14, 8:17 PM, Ian Lepore wrote: On Tue, 2014-04-29 at 13:41 +0800, Julian Elischer wrote: I'm trying to compile a system based on current from just before the 9.x branchpoint. during hte build I got the following message: /usr/bin/ld: this linker was not configured to use sysroots does anyone have any idea what this means in a broader context? did I misconfigure something when I built this system? Julian Are you using ccache? I vaguely remember some reports of this in the past, and I think it was caused by using a version of ccache that wasn't compatible with clang, or something along those lines. -- Ian no I'm using gcc and (as far as I know) no ccache. This is compiling some 3rd party software. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on mips64/mips
TB --- 2014-04-29 15:40:49 - tinderbox 2.21 running on freebsd-current.sentex.ca TB --- 2014-04-29 15:40:49 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014-04-29 15:40:49 - starting HEAD tinderbox run for mips64/mips TB --- 2014-04-29 15:40:49 - cleaning the object tree TB --- 2014-04-29 15:42:02 - /usr/local/bin/svn stat --no-ignore /src TB --- 2014-04-29 15:42:06 - At svn revision 265087 TB --- 2014-04-29 15:42:07 - building world TB --- 2014-04-29 15:42:07 - CROSS_BUILD_TESTING=YES TB --- 2014-04-29 15:42:07 - MAKEOBJDIRPREFIX=/obj TB --- 2014-04-29 15:42:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-04-29 15:42:07 - SRCCONF=/dev/null TB --- 2014-04-29 15:42:07 - TARGET=mips TB --- 2014-04-29 15:42:07 - TARGET_ARCH=mips64 TB --- 2014-04-29 15:42:07 - TZ=UTC TB --- 2014-04-29 15:42:07 - __MAKE_CONF=/dev/null TB --- 2014-04-29 15:42:07 - cd /src TB --- 2014-04-29 15:42:07 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Tue Apr 29 15:42:14 UTC 2014 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Apr 29 16:42:41 UTC 2014 TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m ADM5120 TB --- 2014-04-29 16:42:41 - skipping ADM5120 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m ALCHEMY TB --- 2014-04-29 16:42:41 - skipping ALCHEMY kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m ALFA_HORNET_UB TB --- 2014-04-29 16:42:41 - skipping ALFA_HORNET_UB kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AP121 TB --- 2014-04-29 16:42:41 - skipping AP121 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AP91 TB --- 2014-04-29 16:42:41 - skipping AP91 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AP93 TB --- 2014-04-29 16:42:41 - skipping AP93 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AP94 TB --- 2014-04-29 16:42:41 - skipping AP94 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AP96 TB --- 2014-04-29 16:42:41 - skipping AP96 kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AR71XX_BASE TB --- 2014-04-29 16:42:41 - skipping AR71XX_BASE kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AR724X_BASE TB --- 2014-04-29 16:42:41 - skipping AR724X_BASE kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AR91XX_BASE TB --- 2014-04-29 16:42:41 - skipping AR91XX_BASE kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AR933X_BASE TB --- 2014-04-29 16:42:41 - skipping AR933X_BASE kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m AR934X_BASE TB --- 2014-04-29 16:42:41 - skipping AR934X_BASE kernel TB --- 2014-04-29 16:42:41 - cd /src/sys/mips/conf TB --- 2014-04-29 16:42:41 - /obj/mips.mips64/src/tmp/legacy/usr/sbin/config -m BERI_DE4_BASE TB --- 2014-04-29 16:42:41 - building BERI_DE4_BASE kernel TB --- 2014-04-29 16:42:41 - CROSS_BUILD_TESTING=YES TB --- 2014-04-29 16:42:41 - MAKEOBJDIRPREFIX=/obj TB --- 2014-04-29 16:42:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2014-04-29 16:42:41 - SRCCONF=/dev/null TB --- 2014-04-29 16:42:41 - TARGET=mips TB --- 2014-04-29 16:42:41 - TARGET_ARCH=mips64 TB --- 2014-04-29 16:42:41 - TZ=UTC TB --- 2014-04-29 16:42:41 - __MAKE_CONF=/dev/null TB --- 2014-04-29 16:42:41 - cd /src TB --- 2014-04-29 16:42:41 - /usr/bin/make -B buildkernel KERNCONF=BERI_DE4_BASE Kernel build for BERI_DE4_BASE started on Tue Apr 29 16:42:41 UTC 2014 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree
Re: odd message from ld in -current around 9.0 branchpoint
On 4/29/14, 11:42 PM, Julian Elischer wrote: On 4/29/14, 8:17 PM, Ian Lepore wrote: On Tue, 2014-04-29 at 13:41 +0800, Julian Elischer wrote: I'm trying to compile a system based on current from just before the 9.x branchpoint. during hte build I got the following message: /usr/bin/ld: this linker was not configured to use sysroots does anyone have any idea what this means in a broader context? did I misconfigure something when I built this system? Julian Are you using ccache? I vaguely remember some reports of this in the past, and I think it was caused by using a version of ccache that wasn't compatible with clang, or something along those lines. -- Ian no I'm using gcc and (as far as I know) no ccache. This is compiling some 3rd party software. I just recompiled ld and gcc and it's still not working.. did we break sysroot support some time in 2011? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
What on earth is all this %20 crap at the end of the GUID? (newfs?)
Created a simple partition: root@:~ # gpart create -s gpt da11 da11 created root@:~ # gpart add -t freebsd-ufs da11 da11p1 added root@:~ # gpart show da11 =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) root@:~ # Then run a newfs and reboot the system. Upon reboot this is what I get? =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) =40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% 20%20%20%20 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) What is going on here? sean signature.asc Description: This is a digitally signed message part
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On 04/29/2014 19:51, Sean Bruno wrote: Created a simple partition: root@:~ # gpart create -s gpt da11 da11 created root@:~ # gpart add -t freebsd-ufs da11 da11p1 added root@:~ # gpart show da11 =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) root@:~ # Then run a newfs and reboot the system. Upon reboot this is what I get? =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) =40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% 20%20%20%20 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) What is going on here? sean I'm guessing it is picking up spaces from a physical ID on your disk from /sys/geom/label/g_label_disk_ident.c kern.geom.label.disk_ident.enable=0 in /boot/loader.conf will ignore that class. It was added in 10 and only shows up with certain devices. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On 2014-04-29 19:51, Sean Bruno wrote: Created a simple partition: root@:~ # gpart create -s gpt da11 da11 created root@:~ # gpart add -t freebsd-ufs da11 da11p1 added root@:~ # gpart show da11 =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) root@:~ # Then run a newfs and reboot the system. Upon reboot this is what I get? =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) =40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% 20%20%20%20 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) What is going on here? sean That is highly unusual, does your disk have a bunch of blank spaces in its serial # or something? -- Allan Jude signature.asc Description: OpenPGP digital signature
POLA.. missing --sysroot option in ld?
In our 8.0 based systems at $JOB our build environment made heavy use of the --sysroot option in gcc and ld. We are trying to move up to a newer release but suddenly the --sysroot option has disappeared. we get the message /usr/bin/ld: this linker was not configured to use sysroots Does anyone know what happened? and when, and by who? I have looked in the Makefiles and configuration files in SVN and I can't see a change that would have done this.. of course the building of these tools is rather complex so I may have missed some place.. julian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On Tue, Apr 29, 2014 at 8:30 PM, Allan Jude free...@allanjude.com wrote: On 2014-04-29 19:51, Sean Bruno wrote: Created a simple partition: root@:~ # gpart create -s gpt da11 da11 created root@:~ # gpart add -t freebsd-ufs da11 da11p1 added root@:~ # gpart show da11 =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) root@:~ # Then run a newfs and reboot the system. Upon reboot this is what I get? =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) =40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% 20%20%20%20 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) What is going on here? sean That is highly unusual, does your disk have a bunch of blank spaces in its serial # or something? Not that unusual at all. In ATA and SCSI alike it's common for text fields to be defined as fixed length strings. I've seen many vendors pad their entries out with spaces; for some reason they're allergic to using NULLs. geom should probably be modified to strip trailing whitespace from the serial number. -Alan -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What on earth is all this %20 crap at the end of the GUID? (newfs?)
On Tuesday 29 April 2014 20:52:30 Alan Somers wrote: On Tue, Apr 29, 2014 at 8:30 PM, Allan Jude free...@allanjude.com wrote: On 2014-04-29 19:51, Sean Bruno wrote: Created a simple partition: root@:~ # gpart create -s gpt da11 da11 created root@:~ # gpart add -t freebsd-ufs da11 da11p1 added root@:~ # gpart show da11 =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) root@:~ # Then run a newfs and reboot the system. Upon reboot this is what I get? =40 7814037088 da11 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) =40 7814037088 diskid/DISK-Z1Z0DQ73%20%20%20%20%20%20%20%20% 20%20%20%20 GPT (3.6T) 40 7814037088 1 freebsd-ufs (3.6T) What is going on here? sean That is highly unusual, does your disk have a bunch of blank spaces in its serial # or something? Not that unusual at all. In ATA and SCSI alike it's common for text fields to be defined as fixed length strings. I've seen many vendors pad their entries out with spaces; for some reason they're allergic to using NULLs. geom should probably be modified to strip trailing whitespace from the serial number. In this particular case, it's a modified ciss driver. If memory serves, ciss pads its cam ident strings with spaces and that's showing up here. FWIW, this is usually why I rm -rf /dev/gptid /dev/diskid before doing an import. I don't usually want the synthetic names in there. -Peter -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV UTF-8: for when a ' just won\342\200\231t do. signature.asc Description: This is a digitally signed message part.
Re: POLA.. missing --sysroot option in ld?
On 4/30/14, 10:36 AM, Julian Elischer wrote: In our 8.0 based systems at $JOB our build environment made heavy use of the --sysroot option in gcc and ld. We are trying to move up to a newer release but suddenly the --sysroot option has disappeared. we get the message /usr/bin/ld: this linker was not configured to use sysroots more spefically the following command (from 'configure') fails on near 9 and succeeds on 8.0. configure:3352: /usr/bin/gcc -Wall -Wno-unused-parameter -nostdinc -isystem /usr/build/buildroot/tools/x86_gcc4.2.4/usr/include --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 -Wall -Wno-unused-parame ter -nostdinc -isystem /usr/build/buildroot/tools/x86_gcc4.2.4/usr/include --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 --sysroot /usr/build/buildroot/tools/x86_gcc4.2.4 -L/usr/build/buildroot/too ls/x86_gcc4.2.4/lib -L/usr/build/buildroot/tools/x86_gcc4.2.4/usr/lib conftest.c 5 Does anyone know what happened? and when, and by who? I have looked in the Makefiles and configuration files in SVN and I can't see a change that would have done this.. of course the building of these tools is rather complex so I may have missed some place.. julian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
