Opened 13 years ago
Closed 12 years ago
#32346 closed defect (fixed)
ragel 6.7 fails to build with clang
Reported by: | drbacher@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | clang | Cc: | |
Port: | ragel |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
The ragel 6.7 port fails to build with the clang compiler. The build succeeds with the llvm-gcc-4.2 compiler (as suggested in the ProblemHotlist).
port install ragel configure.compiler=llvm-gcc-4.2 -universal
I had to add "-universal" to work around link errors like:
file was built for unsupported file format which is not the architecture being linked (i386)
Attachments (1)
Change History (4)
comment:1 follow-up: 2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | clang added |
Owner: | changed from macports-tickets@… to mww@… |
Summary: | ragel 6.7 fails to build on 10.7 Lion with Xcode 4.2 → ragel 6.7 fails to build with clang |
Changed 13 years ago by drbacher@…
Attachment: | ragel-clang-main.log added |
---|
ragel main.log compiled under clang
comment:2 Changed 13 years ago by drbacher@…
Replying to ryandesign@…:
Usually you should file a separate ticket for separate issues.
Fair enough. I'll file a separate ticket for the +universal failure.
comment:3 Changed 12 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Replying to drbacher@…:
Could you attach a main.log file from the failed build with clang?
Usually you should file a separate ticket for separate issues.