Move desktop-build compiler/path hacks to their own shell script [TC]

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
a year ago

People

(Reporter: mrrrgn, Assigned: mrrrgn)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

3 years ago
This makes it more obvious which parts of our build process need to be trimmed away in favor of a cleaner approach.
(Assignee)

Updated

3 years ago
Assignee: nobody → winter2718
(Assignee)

Comment 1

3 years ago
Created attachment 8610416 [details] [diff] [review]
compiler.hacks.diff

Next step will be getting rid of them entirely.
Attachment #8610416 - Flags: review?(dustin)
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

3 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 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

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Component: Tools → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.