#40118 closed defect (invalid)
dragonegg-3.0-gcc-4.5 @3.0_2, dragonegg-3.1-gcc-4.5 @3.1_2: build cannot detect LTO
| Reported by: | larryv (Lawrence Velázquez) | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | Cc: | ||
| Port: | dragonegg-3.0-gcc-4.5 dragonegg-3.1-gcc-4.5 |
Description
Both are failing with the same error on 10.8.4.
:info:build Compiling Constants.cpp :info:build /opt/local/var/macports/build/_Users_larryv_Projects_MacPorts_svn_trunk_dports_lang_dragonegg-3.1/dragonegg-3.1-gcc-4.5/work/dragonegg-3.1.src/src/Backend.cpp:1543:3: error: "LTO support required but not enabled in GCC" :info:build # error "LTO support required but not enabled in GCC" :info:build ^ :info:build 13 warnings and 1 error generated. :info:build make: *** [Backend.o] Error 1
The corresponding ports for DragonEgg 3.2, 3.3, and 3.4 build successfully. I have gcc45 @4.5.4_8+universal active.
Attachments (2)
Change History (8)
Changed 11 years ago by larryv (Lawrence Velázquez)
| Attachment: | dragonegg-3.0-gcc-4.5.main.log added |
|---|
Changed 11 years ago by larryv (Lawrence Velázquez)
| Attachment: | dragonegg-3.1-gcc-4.5.main.log added |
|---|
comment:1 follow-up: 2 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jeremyhu@…:
yep.
# LTO doesn't work for other targets, see ticket #32863 if {![variant_isset universal] && $build_arch == "x86_64"} { configure.args-append --enable-lto }
Odd; I wonder why this didn’t crop up before now. Meh.
comment:3 follow-up: 4 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Did you just enable +universal?
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jeremyhu@…:
Did you just enable +universal?
No, I’ve had my GCC ports installed as universal since before you created the DragonEgg subports. I’m pretty sure that revision 1 of dragonegg-3.[01]-gcc-4.5 had built successfully with gcc45 @4.5.4_7+universal.
comment:5 follow-up: 6 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
No, I'm pretty certain that dragonegg never built against gcc45 +unviersal ... since I know that was failing when I pushed the port (I was hitting it myself on my +universal machines).
comment:6 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to jeremyhu@…:
No, I'm pretty certain that dragonegg never built against gcc45 +unviersal ... since I know that was failing when I pushed the port (I was hitting it myself on my +universal machines).
Now that I think about it…
- I flipped the
delete_la_files yes/buildfromsource alwaysswitch. - I uninstalled all my ports.
- I built all my ports—including the GCC and DragonEgg ports—as x86_64.
- I rebuilt select ports—including the GCC ports—as universal.
And maybe I hadn’t encountered the build failure prior to all of that because I’d installed the DragonEgg ports via binary archives.
yep.
# LTO doesn't work for other targets, see ticket #32863 if {![variant_isset universal] && $build_arch == "x86_64"} { configure.args-append --enable-lto }