src/gnu/usr.bin/binutils/Makefile.inc0, branch release/4.1.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-07-26T21:12:35Z

'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

s/MACHINE_ARCH/TARGET_ARCH/g

1999-12-17T15:50:45Z

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.

Change CROSS_TOOLS to CROSS_ARCH because that makes more sense.

1999-11-06T21:13:47Z

Allow for the case where the host architecture might also be listed in CROSS_ARCH, so don't do things twice. This situation can arise if you want NT support in binutils (CROSS_ARCH=i386 CROSS_FORMAT=winnt).

$Id$ -> $FreeBSD$

1999-08-27T23:37:10Z

Add TARGET_ARCH=mipsel and TARGET_ARCH=mipseb as a valid targets.

1999-03-01T04:01:57Z

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.

Update for import of binutils-2.9.1.

1998-09-06T23:01:53Z

Submitted by: Doug Rabson

Add makefile support for cross-architectures. Allow CROSS_TOOLS to

1998-05-04T21:10:56Z

be defined (in /etc/make.conf, say) and set to the additional architectures that need to be compiled in. So on alpha I set CROSS_TOOLS = i386. On i386 you can't build alpha due to lack of 64-bit support on 32-bit architectures, but that's a GNU problem. This change relies on makefiles in the binutils sub-directories having the extension defined in the CROSS_TOOLS, instead of those makefiles being selected based on the host architecture.

Change the include path for bfd.h to libbfd/${MACHINE_ARCH} since

1998-03-12T05:59:22Z

I moved the location of that architecture specific file.

Restructure the binutils hierarchy somewhat in order to better

1998-03-12T02:55:43Z

support building it for variant architectures. It was already becoming clear that the former structure was too rigid and didn't scale well. The usual sort of makefile magic arranges to .include an architecture specific makefile "Makefile.${MACHINE_ARCH}" in each directory where it exists. Also, sources will be found in each subdirectory "${MACHINE_ARCH}" that exists. This is all taken care of automatically by the top level "Makefile.inc0". This all seems to work right for the i386 now. I have also converted those alpha pieces already present to the new schema as best I could. Also: change the BINDIR on the i386 to /usr/libexec/elf for "ar" and "ranlib". They are not object format independent enough to put into /usr/bin.