Re: Problems building Binutils-2.25

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jonathan,

	Thanks for the further reply.

	Checked config.log in obj/ (726 lines) - the "not supported" message is
not present, and there is no other message around the point where ISL is mentioned.
The lines numbers included there helped in locating the relevant place in the
configure script (15859 lines).

	Examined the configure script, and found it checks the target against a
list of non supported ones. The checks include: 
  i[3456789]86-*-darwin*)
    noconfigdirs="$noconfigdirs ld gprof"
    noconfigdirs="$noconfigdirs sim target-rda"
    ;;
  x86_64-*-darwin[912]*)
    noconfigdirs="$noconfigdirs ld gas gprof"
    noconfigdirs="$noconfigdirs sim target-rda"
    ;;

These are later used to set notsupp, used in the message:
"This configuration is not supported..."

	The problem seems to be the changed identification of system types
after my system has been upgraded to Mac OS X 10.9.5 with Kernel
Version: Darwin 13.4.0;  compared with when I built gcc with Mac OS X
10.5.8  Kernel Version: Darwin 9.8.0.

	The reported system types are now:
checking build system type... x86_64-apple-darwin13.4.0
checking host system type... x86_64-apple-darwin13.4.0
checking target system type... x86_64-apple-darwin13.4.0

	but when gcc4.7.2 was compiled:
checking build system type... i386-apple-darwin9.8.0
checking host system type... i386-apple-darwin9.8.0
checking target system type... i386-apple-darwin9.8.0

	This seems to arise from the different information from uname and hostinfo.
	Now:
uname -m = x86_64
uname -r = 13.4.0
uname -s = Darwin
/usr/bin/uname -p = i386
/usr/bin/hostinfo      = Mach kernel version:
	 Darwin Kernel Version 13.4.0: Wed Mar 18 16:20:14 PDT 2015; root:xnu-2422.115.14~1/RELEASE_X86_64
Kernel configured for up to 2 processors.
2 processors are physically available.
2 processors are logically available.
Processor type: i486 (Intel 80486)
Processors active: 0 1
Primary memory available: 2.00 gigabytes

	previously:
uname -m = i386
uname -r = 9.8.0
uname -s = Darwin
/usr/bin/uname -p = i386
/usr/bin/hostinfo      = Mach kernel version:
	 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
Kernel configured for up to 2 processors.
2 processors are physically available.
2 processors are logically available.
Processor type: i486 (Intel 80486)
Processors active: 0 1
Primary memory available: 2.00 gigabytes

	So "the machine hardware name" now differs from "the machine processor architecture name":
x86_64/i386 versus i386/i386.  In both cases they differ from Processor type: i486 (Intel 80486).

	The noconfigdirs seems to eliminate "as/gas" for x86_64 but not for i386, and "ld" for both.

	The existing "as" within the Mac system is in /usr/bin/as, but this seems to use
 /Library/Developer/CommandLineTools/usr/libexec/as/x86_64/as

	There are 3 subdirectories in /Library/Developer/CommandLineTools/usr/libexec/as/
(each with just as):  arm/    i386/   x86_64/

as -v  responds:
Apple Inc version cctools-862, GNU assembler version 1.38

	Since my hardware remains the same from the time when I built gcc4.7.2 (only the
system software has been upgraded), is it possible to build "as" by specifying a target using
i386-apple-darwin13.4.0?

	Thanks,
		Ellis

On 9 Jun 2015, at 09:38, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote:

> Look in config.log
> 
> I do not believe the "not supported in the following subdirectories"
> message is related to ISL






[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux