[buildstream] branch jonathan/source-bundle-workaround created (now 910e6d0)

[no...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

not-in-ldap pushed a change to branch jonathan/source-bundle-workaround
in repository https://gitbox.apache.org/repos/asf/buildstream.git.


      at 910e6d0  Be more explicit on where the gcc dirs are in the bootstrap

This branch includes the following new commits:

     new 910e6d0  Be more explicit on where the gcc dirs are in the bootstrap

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[buildstream] 01/01: Be more explicit on where the gcc dirs are in the bootstrap

[no...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

not-in-ldap pushed a commit to branch jonathan/source-bundle-workaround
in repository https://gitbox.apache.org/repos/asf/buildstream.git

commit 910e6d08f7eb96c9e7d2bc02251b4856263e450b
Author: Jonathan Maw <jo...@codethink.co.uk>
AuthorDate: Thu Sep 14 11:03:04 2017 +0100

    Be more explicit on where the gcc dirs are in the bootstrap
    
    It's possible for the gcc binary to be in /tools, but the libs we want
    to be in /usr/lib. gcc will by default look in a dir related to where it
    found the gcc binary.
---
 buildstream/data/build-module.sh.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/buildstream/data/build-module.sh.in b/buildstream/data/build-module.sh.in
index d67ee9a..0f13706 100644
--- a/buildstream/data/build-module.sh.in
+++ b/buildstream/data/build-module.sh.in
@@ -26,10 +26,14 @@ mkdir -p '{install_root}'
 cp -a "$SRCDIR/{name}/." '{build_root}'
 cd '{build_root}'
 
+# dodgy hack because /usr/bin is a symlink to /tools/bin
+export GCC_EXEC_PREFIX='/usr/lib/gcc/'
+
 export PREFIX='{install_root}'
 
 export {variables}
 
+
 # Build the module
 {commands}