src/gnu/usr.bin/binutils/libbfd, branch release/4.1.0_cvs FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F4.1.0_cvs 2000-07-26T21:12:35Z This commit was manufactured by cvs2svn to create tag 2000-07-26T21:12:35Z cvs2svn cvs2svn@FreeBSD.org 2000-07-26T21:12:35Z urn:sha1:7f1bf9342879a7ee2dd88e11a33ae7509eab55b0 'RELENG_4_1_0_RELEASE'. This commit was manufactured to restore the state of the 4.1-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs. MFC: Upgrade to Binutils 2.10.0. 2000-07-06T22:16:12Z David E. O'Brien obrien@FreeBSD.org 2000-07-06T22:16:12Z urn:sha1:a8460813121e7489510e88202b7b77553ec07e48 s/MACHINE_ARCH/TARGET_ARCH/g 1999-12-17T15:50:45Z Marcel Moolenaar marcel@FreeBSD.org 1999-12-17T15:50:45Z urn:sha1:ecc4dcbd828295057f2272b8c0a2d1ac0a910d92 The target machine is represented by TARGET_ARCH. MACHINE_ARCH always represents the host machine. When TARGET_ARCH is not defined, it is assumed to be equal to MACHINE_ARCH. This means that we're building a native toolset by default. We're creating cross-compilation tools when MACHINE_ARCH != TARGET_ARCH. TARGET_ARCH is defined when building binutils as part of the bootstrap build and is set to reflect the architecture we're currently cross- building. With this change binutils is ready for cross-building. Make binutils for Alpha work on i386 machine, by properly defining 1999-11-12T16:53:58Z Marcel Moolenaar marcel@FreeBSD.org 1999-11-12T16:53:58Z urn:sha1:2205071966973ecbc45b6282c40bd08248360e02 whether the host machine has a 64-bit long or not. Add support for additional architectures. 1999-11-06T21:38:41Z John Birrell jb@FreeBSD.org 1999-11-06T21:38:41Z urn:sha1:53149093a0bba7abb32cda2b32e19ed6a283bc6e Add support for additional architectures. 1999-11-06T21:28:22Z John Birrell jb@FreeBSD.org 1999-11-06T21:28:22Z urn:sha1:015520102a37f441587dd213440773dcbacc4599 Teach binutils how to understand NT format objects and libs. This is useful 1999-11-06T21:09:40Z John Birrell jb@FreeBSD.org 1999-11-06T21:09:40Z urn:sha1:2e734fae4ee336c1db223fd172c1b1925a61cd9a for those who want to objdump --disassemble things that they're not supposed to. 8-) Add a BINUTILSDISTDIR hook to provide a path to a full binutils release 1999-11-06T21:04:46Z John Birrell jb@FreeBSD.org 1999-11-06T21:04:46Z urn:sha1:3ba3ae906a6058c1054e107cb82905e55497110a outside the contrib files that FreeBSD distributes. This for use by those who want to work on porting FreeBSD to additional architectures. $Id$ -> $FreeBSD$ 1999-08-27T23:37:10Z Peter Wemm peter@FreeBSD.org 1999-08-27T23:37:10Z urn:sha1:9b7a44a60e11baaf94f68f81c4b30d26f31643b7 Add TARGET_ARCH=mipsel and TARGET_ARCH=mipseb as a valid targets. 1999-03-01T04:01:57Z Warner Losh imp@FreeBSD.org 1999-03-01T04:01:57Z urn:sha1:7408d8ff343a0912c2c2850d08a4b740c23af690 Unlike the unisex architecutres we've had so far, mips is bisexual. These tools can produce either byte sex, and the compiler/make determines the proper gender to use. Otherwise, we'd have to have had mipsel and mipseb in all the places that we have just mips. And there are other complications with doing that (binutils doesn't like to build mips tools without both byte genders, it seems). Introduced BINUTIL_ARCH so that other bisexual architectures can a generic mechanism. We cannot just define MACHINE_ARCH as mips because we need to differentiate big and little endian types of binaries. Discussions on freebsd-arch have hashed out this issue (and the parallel libc issues). NetBSD is moving towards mipsel and mipseb for their two flavors of mips ports (in time for 1.4, if this change hasn't already been accomplished). I've been building i386 worlds with this tree for a three months with these files in place with no ill effects.