Opened 9 years ago

Closed 9 years ago

#33250 closed defect (invalid)

libewf: build failure with clang

Reported by: arya.irani@… Owned by: opendarwin.org@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: clang Cc:
Port: libewf

Description (last modified by ryandesign (Ryan Schmidt))

--->  Building libewf
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Failed to install libewf
Log for libewf is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_libewf/libewf/main.log
Error: The following dependencies were not installed: libewf ntfs-3g fuse4x fuse4x-kext
sudo port install testdisk configure.compiler=llvm-gcc-4.2

Attachments (2)

testdisk-main.log (807.2 KB) - added by arya.irani@… 9 years ago.
testdisk build log
testdisk-main.2.log (28.9 KB) - added by arya.irani@… 9 years ago.
testdisk build log

Download all attachments as: .zip

Change History (6)

comment:1 Changed 9 years ago by arya.irani@…

Build resumed ok (including libewf) using sudo port install testdisk configure.compiler=llvm-gcc-4.2

Changed 9 years ago by arya.irani@…

Attachment: testdisk-main.log added

testdisk build log

Changed 9 years ago by arya.irani@…

Attachment: testdisk-main.2.log added

testdisk build log

comment:2 Changed 9 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)
Keywords: clang added
Owner: changed from macports-tickets@… to opendarwin.org@…
Port: libewf added
Summary: 'libewf' (required for 'testdisk') fails to build with default compilerlibewf: build failure with clang

What you've reported is slightly confusing because the output you show in the ticket description is libewf failing to build but the logs you've attached are testdisk failing to build. I believe you're saying that both libewf and testdisk do not build with clang and they both need llvm-gcc-4.2 instead.

This ticket will be only about libewf. Ticket #33219 already exists for testdisk.

comment:3 Changed 9 years ago by arya.irani@…

Yes, it is confusing, sorry! Initially, libewf failed to build.

Per the ProblemHotlist, I tried rebuilding with llvm-gcc-4.2, and the build succeeded. Then I realized I should have attached the libewf build failure log, but it was gone --- perhaps as a result of the eventually successful build.

I tried to uninstall libewf and tried to reproduce the failed build by using port uninstall testdisk; port uninstall libewf; port install testdisk , but could not reproduce the failed libewf build. I don't know why.

comment:4 Changed 9 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

Yes, MacPorts deletes logs of successful installs. If you want to keep logs of successful installs, edit macports.conf and set "keeplogs" to "yes".

I don't have Xcode 4 or Lion, but I cannot reproduce the problem when I tell MacPorts to build libewf with clang; it builds fine with either Apple clang 1.7 that comes with Xcode 3.2.6 ("sudo port -d destroot libewf configure.compiler=clang") or clang 3.0 that's available in the MacPorts clang-3.0 port ("sudo port -d destroot libewf configure.cc=clang-mp-3.0 configure.cxx=clang++-mp-3.0").

Since you're not able to reproduce the build failure with clang either, and we have no main.log to go on, I'll close this as invalid. If further information comes to light later, feel free to re-open.

Note: See TracTickets for help on using tickets.