[MacPorts] #33250: libewf: build failure with clang

MacPorts noreply at macports.org
Fri Mar 23 12:12:01 PDT 2012


#33250: libewf: build failure with clang
-----------------------------------+----------------------------------------
  Reporter:  arya.irani@…          |       Owner:  opendarwin.org@…          
      Type:  defect                |      Status:  closed                    
  Priority:  Normal                |   Milestone:                            
 Component:  ports                 |     Version:  2.0.3                     
Resolution:  invalid               |    Keywords:  clang                     
      Port:  libewf                |  
-----------------------------------+----------------------------------------
Changes (by ryandesign@…):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/33250#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list