Closed
Bug 1168093
Opened 9 years ago
Closed 9 years ago
Move desktop-build compiler/path hacks to their own shell script [TC]
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mrrrgn, Assigned: mrrrgn)
Details
Attachments
(1 file)
2.78 KB,
patch
|
dustin
:
review+
|
Details | Diff | Splinter Review |
This makes it more obvious which parts of our build process need to be trimmed away in favor of a cleaner approach.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → winter2718
Assignee | ||
Comment 1•9 years ago
|
||
Next step will be getting rid of them entirely.
Attachment #8610416 -
Flags: review?(dustin)
Comment 2•9 years ago
|
||
Comment on attachment 8610416 [details] [diff] [review] compiler.hacks.diff Review of attachment 8610416 [details] [diff] [review]: ----------------------------------------------------------------- ::: testing/docker/desktop-build/hacks.sh @@ +7,5 @@ > +# On ubuntu, the compiler that pip detects (x86_64-linux-gnu-gcc) is not > +# available in the tooltool compiler, so we end up using the system default; > +# to get around this, we link to the tooltool compiler that we'd prefer to use. > +mv /usr/bin/x86_64-linux-gnu-gcc /usr/bin/x86_64-linux-gnu-gcc.orig > +ln -s /home/worker/workspace/build/src/gcc/bin/gcc /usr/bin/x86_64-linux-gnu-gcc Does this work at this point in the Dockerfile? Or in docker at all, before tc-vcs has checked out the source?
Assignee | ||
Comment 3•9 years ago
|
||
Yes(In reply to Dustin J. Mitchell [:dustin] from comment #2) > Comment on attachment 8610416 [details] [diff] [review] > compiler.hacks.diff > > Review of attachment 8610416 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: testing/docker/desktop-build/hacks.sh > @@ +7,5 @@ > > +# On ubuntu, the compiler that pip detects (x86_64-linux-gnu-gcc) is not > > +# available in the tooltool compiler, so we end up using the system default; > > +# to get around this, we link to the tooltool compiler that we'd prefer to use. > > +mv /usr/bin/x86_64-linux-gnu-gcc /usr/bin/x86_64-linux-gnu-gcc.orig > > +ln -s /home/worker/workspace/build/src/gcc/bin/gcc /usr/bin/x86_64-linux-gnu-gcc > > Does this work at this point in the Dockerfile? Or in docker at all, before > tc-vcs has checked out the source? Yes. I built mrrrgn/desktop-build:12 with this.
Comment 4•9 years ago
|
||
Comment on attachment 8610416 [details] [diff] [review] compiler.hacks.diff Review of attachment 8610416 [details] [diff] [review]: ----------------------------------------------------------------- ::: testing/docker/desktop-build/hacks.sh @@ +7,5 @@ > +# On ubuntu, the compiler that pip detects (x86_64-linux-gnu-gcc) is not > +# available in the tooltool compiler, so we end up using the system default; > +# to get around this, we link to the tooltool compiler that we'd prefer to use. > +mv /usr/bin/x86_64-linux-gnu-gcc /usr/bin/x86_64-linux-gnu-gcc.orig > +ln -s /home/worker/workspace/build/src/gcc/bin/gcc /usr/bin/x86_64-linux-gnu-gcc Ah, I read the link backward -- I was thinking it would be a problem that build/src didn't exist yet, but of course it's not.
Attachment #8610416 -
Flags: review?(dustin) → review+
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•