#44576 closed defect (fixed)
dragonegg-3.3-gcc-4.8 fails to upgrade
| Reported by: | MartinBuchmann (Martin Buchmann) | Owned by: | NicosPavlov |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.1 |
| Keywords: | Cc: | petrrr, evandrix (Lee Wei Yeong), larryv (Lawrence Velázquez), gnw3 | |
| Port: | dragonegg-3.3-gcc-4.8 |
Description
Hi,
I tried to upgrade dragonegg-3.3-gcc-4.8 from version 3.3_7 to 3.3_8 but it fails during building, see attached log.
Regards
Martin
Attachments (5)
Change History (19)
Changed 10 years ago by MartinBuchmann (Martin Buchmann)
| Attachment: | dragonegg.log added |
|---|
comment:1 Changed 10 years ago by mf2k (Frank Schima)
| Cc: | jeremyhu@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to jeremyhu@… |
comment:2 Changed 10 years ago by petrrr
| Cc: | petr@… added |
|---|
comment:5 Changed 10 years ago by petrrr
I observe the same build problem, both for dragonegg-3.3-gcc-4.8 and dragonegg-3.4-gcc-4.8. Attaching the respective main.log files.
Changed 10 years ago by petrrr
| Attachment: | dragonegg-3.3-gcc-4.8.main.log added |
|---|
Changed 10 years ago by petrrr
| Attachment: | dragonegg-3.4-gcc-4.8.main.log added |
|---|
comment:7 Changed 10 years ago by gnw3
This looks like the same issue (ABIHack.inc:1666:36: error: 'TARGET_CPU_DEFAULT_max' was not declared in this scope) reported as FTBFS in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735754 which was resolved as "fixed upstream".
comment:8 Changed 10 years ago by NicosPavlov
The fix upstream corresponds to http://llvm.org/bugs/show_bug.cgi?id=18548. Applying the patch to the Portfile fixes the build (attached). Apparently, the port dragonegg-3.4-gcc-4.8 has the same issue.
Changed 10 years ago by NicosPavlov
| Attachment: | patch-Portfile.diff added |
|---|
Changed 10 years ago by NicosPavlov
| Attachment: | patch-CPU_DEFAULT.patch added |
|---|
comment:9 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Owner: | changed from jeremyhu@… to nicos@… |
|---|
Feel free to push whatever changes you want to dragonegg. It should be openmaintainer (I'll double check that now).
comment:11 Changed 10 years ago by NicosPavlov
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:12 follow-up: 14 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
It still reportedly fails to build. See #45720. Did this fix the build problem for you or just get you one step closer?
comment:13 Changed 10 years ago by MartinBuchmann (Martin Buchmann)
I just tried to build version 3.3_13 of dragonegg-3.3-gcc-4.8 and it builds fine on my system.
comment:14 Changed 10 years ago by NicosPavlov
Replying to jeremyhu@…:
It still reportedly fails to build. See #45720. Did this fix the build problem for you or just get you one step closer?
The fix solved the issue so that I could get fine builds. I did not experience other issues. However, I did the fix on 10.9, and confirmed the build later on 10.10. The issue reported in #45720 seems to happen on 10.8. This may be due to a difference in the build systems.
Cc Me!