#46013 closed defect (fixed)
gambit-c @4.7.3 build times out
Reported by: | jmroot (Joshua Root) | Owned by: | nerdling (Jeremy Lavergne) |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | Cc: | ||
Port: | gambit-c |
Description
https://build.macports.org/builders/buildports-yosemite-x86_64/builds/44
This blocks all the ports that come after it from being built: https://build.macports.org/builders/buildports-yosemite-x86_64/builds/39
Change History (7)
comment:1 Changed 10 years ago by nerdling (Jeremy Lavergne)
Keywords: | yosemite added |
---|
comment:2 Changed 10 years ago by nerdling (Jeremy Lavergne)
Also, I was able to build this successfully:
The following ports are currently installed: gambit-c @4.7.3_0 (active) platform='darwin 14' archs='x86_64'
Seems the issue is unique to the Mac OS Forge buildslave.
comment:3 Changed 10 years ago by jmroot (Joshua Root)
Keywords: | yosemite removed |
---|
https://build.macports.org/builders/buildports-lion-x86_64/builds/25196
https://build.macports.org/builders/buildports-mtln-x86_64/builds/19442
https://build.macports.org/builders/buildports-mavericks-x86_64/builds/8864
Yes the issue is specific to buildbot, that’s what imposes the timeout.
comment:4 Changed 10 years ago by jmroot (Joshua Root)
configure: ************************************************************************** *** *** *** The option "--enable-single-host" was specified to the configure *** *** script and a LLVM C compiler is being used (clang or LLVM GCC). *** *** This combination is not recommended as the build may require a *** *** lot of memory and a very long time (over 30 minutes on a fairly *** *** fast machine with clang 3.0). Configuring with GNU GCC will give *** *** a faster build (1 min on the same machine with GNU GCC 4.2.1) and *** *** the executable will be faster. *** *** *** **************************************************************************
comment:5 Changed 10 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:6 follow-up: 7 Changed 10 years ago by nerdling (Jeremy Lavergne)
The option you disabled is highly recommended by upstream; disabling it guarantees slowdowns. Why not fix the timeout rather than crippling the builds?
comment:7 Changed 2 years ago by barracuda156
Replying to nerdling:
The option you disabled is highly recommended by upstream; disabling it guarantees slowdowns. Why not fix the timeout rather than crippling the builds?
It is not disabled, it is used with GCC.
This only impacts yosemite.