Bug 195998 - arm release builds rely on having a host gcc
Summary: arm release builds rely on having a host gcc
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-arm (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-15 15:30 UTC by Ed Maste
Modified: 2017-06-26 02:09 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Maste freebsd_committer freebsd_triage 2014-12-15 15:30:56 UTC 
The ARM release builds require u-boot, and u-boot's build infrastructure (for at least certain versions) is hardcoded to use a host gcc. This is currently handled by explicitly building and installing in gnu/usr.bin/cc but this will not be possible once gcc 4.2.1 is removed from the source tree.

I suspect u-boot is just building some basic host tools and it may be possible to just make a symlink cc -> gcc in the chroot for the builds.

See also https://reviews.freebsd.org/D1317
Comment 1 Ian Lepore freebsd_committer freebsd_triage 2014-12-15 15:36:14 UTC 
The mechanism for building u-boot for ARM images is transitioning towards ports/packages as the build mechanism.  See sysutils/u-boot-beaglebone and other u-boot-* ports.
Comment 2 Ian Lepore freebsd_committer freebsd_triage 2016-01-02 04:36:20 UTC 
I just stumbled across this.  We're completely converted to using u-boot ports now, right?  Does that mean the changes to release.sh to pre-build gperf should be reverted?  And should this PR be closed as OBE?
Comment 3 Ed Maste freebsd_committer freebsd_triage 2017-06-26 02:09:30 UTC 
Rework by gjb in r282553 seems to have addressed this.