pkg/toolchains/gcc-4.7.git - "gcc-4.7" package (replaced by pkg/gcc.git)

	Commit message (Collapse)	Author	Age	Files	Lines
*	targets.d/i686-linux-glibc.sh: New file.	P. J. McDermott	2014-01-27	1	-0/+5
\|
*	targets.d/core-linux-eglibc.sh: Remove.	P. J. McDermott	2014-01-27	1	-5/+0
\|
*	targets.d/amd64-linux-glibc.sh: New file.	P. J. McDermott	2014-01-27	1	-0/+5
\|
*	Set target options when configuring GCC.	P. J. McDermott	2013-06-28	1	-0/+1
\|
*	Don't use GNU system type dir in target fragment.	P. J. McDermott	2013-06-14	1	-1/+1
\|
*	Use GNU system type multiarch dir for transition.	P. J. McDermott	2013-06-05	1	-1/+1
\|
*	Also edit MULTILIB_OSDIRNAMES in target fragment.	P. J. McDermott	2013-06-04	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The GCC Internals manual (gcc/doc/fragments.texi) says: > For configurations that support both multilib and multiarch, > MULTILIB_OSDIRNAMES also encodes the multiarch name, thus subsuming > MULTIARCH_DIRNAME. > [...] > > MULTIARCH_DIRNAME is not used for configurations that support both multilib > and multiarch. In that case, multiarch names are encoded in > MULTILIB_OSDIRNAMES instead. This sounds like the makefile macro used depends on the build-time user configuration; that is, the options --disable-multilib and --enable-multiarch should cause MULTIARCH_DIRNAME to be used. Instead, it seems MULTILIB_OSDIRNAMES is used, even if multilib is disabled. So apparently, "configurations that support both" means GCC target configurations that support both features, not build-time user configurations that enable them.
*	Enable multiarch and set MULTIARCH_DIRNAME.	P. J. McDermott	2013-06-04	1	-0/+1
\| \| \| \|	This should add /usr/include/<target> to the include search list.
*	Edit default ELF INTERP paths in GCC config files.	P. J. McDermott	2013-04-27	1	-0/+2