Opened 10 years ago
Closed 10 years ago
#12075 closed bug (invalid)
Nightly build fails - MIT licence not in packages
Reported by: | haiqu | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Build System | Version: | R1/Development |
Keywords: | MIT | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
Since yesterday (May 19th 2015) nightly fails with missing MIT licence in about 10 packages.
Change History (2)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
One of the reasons why the build process consists of two phases (configure and jam) is because jam can't do certain things like executing a command (e.g. gcc --version
) and processing its output. Even if it could, there are certain checks -- like this -- we really don't want to do in order to avoid slowing the build warm-up down.
Note:
See TracTickets
for help on using tickets.
OK, I got to the bottom of this one.
Evidently I tried to build while gcc-4.8.4 was selected. The reason it confused me is that the errors only showed at the end of the build, but since most of it was already made the build process skipped compiling a lot of stuff.
To fix: Selected gcc-2.95.3, did a
jam clean
and rebuilt.Please change title to "Jam doesn't check for gcc-2.95.3 before building hybrid"