[MacPorts] #24243: libproxy 0.4.0 build failure 10.4.11

MacPorts noreply at macports.org
Tue Mar 30 00:57:47 PDT 2010


#24243: libproxy 0.4.0 build failure 10.4.11
--------------------------------+-------------------------------------------
 Reporter:  stephen@…           |       Owner:  devans@…           
     Type:  defect              |      Status:  new                
 Priority:  Normal              |   Milestone:                     
Component:  ports               |     Version:  1.8.99             
 Keywords:  tiger               |        Port:  libproxy           
--------------------------------+-------------------------------------------

Comment(by ryandesign@…):

 Replying to [ticket:24243 stephen@…]:
 > Build fails because libraries are expected to be in
 /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib, not /opt/local/lib.
 >
 > I wonder if Apple g++-4.0 on 10.4.11 PPC confuses the -isysroot flag
 with the --sysroot flag.  Or maybe it's CMake weirdness.  I've never seen
 anything like this before.

 We've seen this many, many times before. It is unique to Tiger on PowerPC.
 You can workaround the problem by creating the symlink
 /Developer/SDKs/MacOSX10.4u.sdk/opt pointing to /opt. The correct fix for
 the portfile is to ensure all the necessary library link statements are
 present. For example, "can't open dynamic library:
 /Developer/SDKs/MacOSX10.4u.sdk/opt/local/lib/libenchant.1.dylib
 referenced from: /opt/local/lib/libwebkit-1.0.dylib" means the library
 link statement "-lenchant" was missing.

 The next problem here is that libproxy shouldn't be using libwebkit at
 all, since that comes from the webkit-gtk port on which libproxy does not
 declare a dependency.

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


More information about the macports-tickets mailing list