Date: Sun, 16 Nov 2014 15:36:03 -0800 From: Garrett Cooper <yaneurabeya@gmail.com> To: sbruno@freebsd.org Cc: freebsd-arch@freebsd.org Subject: Re: mips misbehaving, not respecting make.conf Message-ID: <735BCED8-EBC1-4B65-AA34-1866ECDF3070@gmail.com> In-Reply-To: <1416179733.1098.1200.camel@bruno> References: <1416179733.1098.1200.camel@bruno>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Nov 16, 2014, at 15:15, Sean Bruno <sbruno@ignoranthack.me> wrote: > I have set make.conf to use AS=/nxb-bin/usr/bin/as and > CC=/nxb-bin/usr/bin/cc > > Yet, while monitoring, I still see the ports build process > using /usr/bin/as and /usr/bin/ld and /usr/libexec/cc1 > > I don't see this on armv6 when building in a jail + qemu. > > I'm trying to understand what is missing from our gcc toolchain here > that is causing the builds to ignore my directives. It all kinds of boils down to this bug with the configuration of our base system copy of gcc: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192394 . The prefixing/sysroot isn’t being setup properly, which means that you have to use $PATH to tell gcc and friends which tool you want to use (which make buildworld, etc does). One way to fix this (if we used autoconf in the base system build) would be to reconfigure it with a particular sysroot: $ ./configure --help | grep -A 3 sysroot --with-build-sysroot=sysroot use sysroot as the system root during the build --with-sysroot=DIR Search for usr/lib, usr/include, et al, within DIR. --with-gnu-ld assume the C compiler uses GNU ld default=no --with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib --without-libiconv-prefix don't search for libiconv in includedir and libdir $ svn info configure | grep ^URL: URL: svn+ssh://ngie@svn.freebsd.org/base/head/contrib/gcc/configure I believe clang is smart enough to compile/link because it is setup to grok multiple formats, but I’ll defer to the clang team to definitively state whether or not that’s the case. Thanks! [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUaTTjAAoJEMZr5QU6S73eN/IH/izZ0W+aWsLOLrSZsLeFYRgA DLKnZ24aSynyStdPzowUaisET5G8T/Pd5ccN3C2AgtugpW3B77niLggj0JyTOowZ gowt4K0rg+1kmA7d/nuMQG84lkcanJ2nU/7PZMpDPGr7aYUzQMRih7TzBGdLkcPf TxAfh3wdqv60U8E7c3UMma964ASxuciSZqFvpViVZV8fNt6Lm9GcDRhDJVSIAzZ5 nuDXntD6JTVHppt93uKJdkRpBhW8rOios5hzTav+tdmCtYAqIWV2wpHoRSALkhjD nR4yoaLa1ADZL19cwgwZ0192s2eZ4EAZrVeH9eLWbWExoWNCmqnX36lxcv4cxxk= =ir13 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?735BCED8-EBC1-4B65-AA34-1866ECDF3070>