Age | Commit message (Collapse) | Author |
|
|
|
|
|
we build perl itself. We need perl to run Configure *after* the
other libraries are installed, since Configure looks at what symbols
exist in libc and the other libs. If anfd when other things in the tree
link against libperl we may need to revisit this issue.
|
|
|
|
|
|
|
|
|
|
- add cross-obj, cross-depend, cross-clean and cross-cleandir targets
- add dependencies between the cross-tools targets
- simplify cross-binutils
- build a cross c++ compiler
- use distribution-etc-root-var in etc for preparing ${CROSSDIR}
ok art@, miod@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cross tools and kernels with those cross tools on all archs except mvme88k
and hppa.
1. Pass MACHINE_ARCH, not MACHINE to TARGET_MACHINE_ARCH when building old
binutils.
2. Instead of using the "intelligent" cpp voodoo to find out MACHINE_ARCH
from MACHINE (which has never worked correctly for sparc, 68k and
recently it broke for powerpc), we have a table of machine->machine_arch
translations. It's easier to modify one table once per arch instead of
juggling for a few hours every time some include files change.
3. Remove some sparc64 cruft.
4. Set MACHINE and MACHINE_ARCH in cross-env, otherwise the kernel will
try to build libkern for the host.
Please note that this doesn't allow you to do complete builds. I haven't
even tested cross-lib. Only kernel builds have been tested.
|
|
o Enable c++.
o Add missing lib/apache/xml/include directory.
o Use lorder from /usr/bin.
art@, mickey@ ok.
|
|
|
|
got broken but let's blame art since he commits into cross-tools all by himself all the time and breaks it
|
|
need to be set for cross building:
cd /usr/src/sbin/init
make `cd /usr/src ; make TARGET=sparc64 cross-env`
Also, xcpp was wrong, cccp is wrong, cpp is probably better.
|
|
|
|
We simply make sure that there always is a TARGET_CANON-X and an X
regardless of which one is the regular file and which one is the symlink.
(this is for cross-tools)
|
|
|
|
--
Ok'd by art@
|
|
of building cross-tools.
|
|
--
Ok'd by deraadt@
|
|
|
|
|
|
- remove extra subshells;
- use exec on terminal commands, avoiding dangling shells that don't
control anything.
More correct:
- use && some more;
- remove `-' in front of includes, so that failures WILL fail...
Okay millert@, deraadt@
|
|
|
|
|
|
pmax libs. I have yet to test that they actually work though.
|
|
broken too
|
|
|
|
|
|
Pass the same --disable-foo flags as we do in gnu/usr.bin/binutils
This allows me to build alpha -> alpha binutils (Don't ask).
|
|
Closes PR 1246
|
|
during the lib install stage too.
|
|
will do that.
|
|
|
|
|
|
|
|
|
|
|
|
make includes, too, by not fixing it. Gee, thanks.
|
|
installation of includes can happen. Do these before and not run via ${SUDO}.
|
|
Many cross-tools cleanups:
o remove mkdirs from the front of each of the rules, but instead have them
depend on new target cross-dirs, which makes all the directories
o Add new target, cross-dirs, to create the directories and symlinks. Before
the symlinks in /usr/cross/$TARGET/blah-unknown-openbsd2.4 were
never right.
o KLUDGE for arc/pmax. MACHINE_ARCH is mips for these machines, but they
differ from other machines in that they use mipsel-unknown-openbsd
for their gnu config string (failure to have the el causes big endian tools
to be built).
These fixes allow me to build a usable toolchain and libraries for
OpenBSD/arc on FreeBSD/i386 (with a few fixes to FreeBSD as well). I
can also build a bootable kernel on the FreeBSD box.
I'd like to add a cross-build target shortly that will build
cross-tools, then will build and install stuff in DESTDIR with the
cross tools living in ${DESTDIR}/usr/cross/${TARGET}.
|
|
o Don't build kerberos if KERBEROS==no
o Use the lorder in the target tree, rather than relying on the
system's lorder to do the right thing in a cross build environment.
|
|
Also build the kerberos libs for the cross environment
|
|
|