Daniel Price <daniel.price@gmail.com> [Mon, 19 Nov 2012 15:20:13 -0800] rev 3128
scripts: unquoted variable reference in glibc-eglibc.sh-common
Signed-off-by: Daniel Price <daniel.price@gmail.com>
Message-Id: <12f092a95a94bcf76912.1353367250@redfish.dssd.com>
Patchwork-Id: 200215
(transplanted from 51160d293e1fdbd69305310d3b34aa0054ce2399)
"Yann E. MORIN" <yann.morin.1998@free.fr> [Thu, 22 Nov 2012 19:43:26 +0100] rev 3127
scripts/functions: fix debug-shell
Properly catch resuming the build when continuing past the
failed command.
The 'case ;;&' construct is a bash4ism. Get rid of it.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Daniel Price <daniel.price@gmail.com> [Tue, 20 Nov 2012 16:59:17 -0800] rev 3126
scripts: refine static linking check to better guide the user
The current mechanism to check if static linking is possible, and the mesage
displayed on failure, can be puzzling to the unsuspecting user.
Also, the current implementation is not using the existing infrastructure,
and is thus difficult to enhance with new tests.
So, switch to using the standard CT_DoExecLog infra, and use four tests to
check for the host compiler:
- check we can run it
- check it can build a trivial program
- check it can statically link that program
- check if it statically link with libstdc++
That should cover most of the problems. Hopefully.
(At the same time, fix a typo in a comment)
Signed-off-by: Daniel Price <daniel.price@gmail.com>
[yann.morin.1998@free.fr: split original patch for self-contained changes]
[yann.morin.1998@free.fr: use steps to better see gcc's output]
[yann.morin.1998@free.fr: commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <163f86b5216fc08c672a.1353459722@nipigon.dssd.com>
Patchwork-Id: 200536
Daniel Price <daniel.price@gmail.com> [Tue, 20 Nov 2012 16:59:17 -0800] rev 3125
scripts: fail on ':' in paths
Signed-off-by: Daniel Price <daniel.price@gmail.com>
[yann.morin.1998@free.fr: split original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <163f86b5216fc08c672a.1353459722@nipigon.dssd.com>
Patchwork-Id: 200536
"Yann E. MORIN" <yann.morin.1998@free.fr> [Mon, 19 Nov 2012 22:13:11 +0100] rev 3124
scripts: fix mis-alignment due to new variables
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Yann Diorcet <diorcet.yann@gmail.com> [Mon, 19 Nov 2012 11:21:31 +0100] rev 3123
binutils: introduce the infrastructure to support binutils alternatives
Rework binutils in order to provide soon binutils alternative.
Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
"Yann E. MORIN" <yann.morin.1998@free.fr> [Mon, 19 Nov 2012 23:24:49 +0100] rev 3122
binutils/elf2flt: remove use of CVS snapshots
The CVS snapshot options are never used, so get rid of them.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Yann Diorcet <diorcet.yann@gmail.com> [Mon, 19 Nov 2012 21:45:09 +0100] rev 3121
binutils/binutils: simplify gold dependencies
In preparation of adding a new kernel-type, Yann D. came up
with a change in semantic on binutils/gold availability.
So far, it was architectures' responsibility to declare that
they did support binutils/gold or not. It makes much more sense
that binutils/gold declares its own availability depending on
the current architecture; after all, architectures have no way
to know wether gold supports them, while gold does know it.
Signed-off-by:Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
Yann Diorcet <diorcet.yann@gmail.com> [Mon, 19 Nov 2012 21:39:58 +0100] rev 3120
binutils: cleanup ELF/FLAT/FDPIC dependencies
In preparation of adding a new kernel-type, Yann D. came up
with a cleanup pass on the ELF/FLAT/FDPIC dependencies.
Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
Yann Diorcet <diorcet.yann@gmail.com> [Fri, 16 Nov 2012 15:25:57 +0100] rev 3119
scripts: add BUILD/HOST extra cflags/ldflags
On some hosts, and for certain toolchains (eg. toolchain targetting
the upcoming Darwin), it may be necessary to pass arbitrary CFLAGS
and/or LDFLAGS when building the components.
And necessary infrastructure:
- EXTRA_{CFLAGS,LDFLAGS}_FOR_{BUILD,HOST} as config options
- pass those extra flags to components
Fix-up a slight typo in elf2flt at the same time (misnamed cflags).
Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com>
Message-Id: <d24043276c9243a35421.1353077450@macbook-smorlat.local>
Patchwork-Id: 199645