Total confusion over toolchain/xdev behavior
Tim Kientzle
tim at kientzle.com
Tue Jul 8 02:59:29 UTC 2014
On Jul 6, 2014, at 4:07 PM, Sean Bruno <sbruno at ignoranthack.me> wrote:
> Objective: install an xcompile toolchain into a jail for use by
> poudriere during arm/mips/sparc/power ports pkgs builds. The build
> should be possible from a non-root user.
>
> As far as I can tell, the xdev target is completely busted for non-clang
> arch's right now as it tries to build clang no matter what I do.
I think you can avoid that if you specify both:
WITHOUT_CLANG=t WITHOUT_CLANG_BOOTSTRAP=t
> Its missing some pretty key documentation to making it work correctly, so a
> lot of my attempts have been "guess and check" with verbose make.
Some of the complexity here might just be that ‘xdev’ is currently
trying to do too much. I think I would find it simpler to use if
it were a handful of separate targets:
# Build and install a cross-GCC using the in-tree sources
make XDEV=arm XDEV_ARCH=armv6 xdev-gcc
# Build and install a cross-clang using the in-tree sources
make XDEV=arm XDEV_ARCH=armv6 xdev-clang
# Build and install cross-binutils using the in-tree sources
make XDEV=arm XDEV_ARCH=armv6 xdev-binutils
# Build and install cross-libraries
# Prerequisite: (xdev-gcc or xdev-clang) and xdev-binutils
make XDEV=arm XDEV_ARCH=armv6 xdev-libs
# Have I missed anything?
If I understand correctly, xdev-clang in many cases
could install symlinks to the host clang without
actually building anything. (If I’m right about that,
maybe we could consider installing those symlinks
for every architecture as part of the default base system.)
Tim
More information about the freebsd-arch
mailing list