Opened 10 years ago

Closed 10 years ago

#27732 closed defect (invalid)

flex fails to find libintl.dylib

Reported by: tlax@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: mww@…, ryandesign (Ryan Schmidt)
Port: flex

Description (last modified by ryandesign (Ryan Schmidt))

Trolliluola:~ tlax$ sudo port install wine-devel
--->  Computing dependencies for wine-devel
--->  Configuring wine-devel
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Log for wine-devel is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_wine-devel/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Attachments (1)

main.log (79.7 KB) - added by tlax@… 10 years ago.
wine-devel main.log

Download all attachments as: .zip

Change History (9)

Changed 10 years ago by tlax@…

Attachment: main.log added

wine-devel main.log

comment:1 Changed 10 years ago by tlax@…

Noticed also that flex spurts out something like this:

Trolliluola:~ tlax$ flex
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/flex
  Reason: no suitable image found.  Did find:
	/opt/local/lib/libintl.8.dylib: no matching architecture in universal wrapper
	/usr/local/lib/libintl.8.dylib: no matching architecture in universal wrapper
Trace/BPT trap

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

Cc: mww@… ryandesign@… added
Description: modified (diff)
Port: flex added
Priority: HighNormal
Summary: wine-devel and wine fail to build on snow leopard (problem with flex)flex fails to find libintl.dylib

Please use WikiFormatting so your posts are legible, and fill in the Port and Cc fields appropriately.

From your log, we see that wine-devel fails to build because it cannot run flex. And as you found, flex cannot run because it has problems using your gettext library. It says there's no matching architecture, so it would be interesting to know what architecture /opt/local/bin/flex and /opt/local/lib/libintl.8.dylib were built for. "lipo -info" can tell you.

The fact that something in /usr/local is found could indicate a problem. Software in /usr/local frequently interferes with software installed by MacPorts, so please remove anything in /usr/local before trying again. Also, if you have any environment variables like DYLD_LIBRARY_PATH set, unset them.

comment:3 Changed 10 years ago by tlax@…

Trolliluola:~ tlax$ lipo -info /opt/local/bin/flex
Non-fat file: /opt/local/bin/flex is architecture: x86_64
Trolliluola:~ tlax$ lipo -info /opt/local/lib/libintl.8.dylib 
Architectures in the fat file: /opt/local/lib/libintl.8.dylib are: ppc7400 i386 
Trolliluola:~ tlax$ sudo port installed|grep gettext
  gettext @0.18.1.1_2+universal (active)
  p5-locale-gettext @1.05_3+universal (active)
Trolliluola:~ tlax$ sudo port installed|grep flex
  flex @2.5.35_0 (active)

Not sure if this is even the problem, but I tried to build flex with +universal, but the configure failed at the same problem. Am I missing something trivial?

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

Ok, so flex is built for x86_64 (this is normal for Snow Leopard) and gettext is built for i386 and ppc (this is not normal). i386 ppc is what you get if you build universal on Leopard and earlier. Check your /opt/local/etc/macports/macports.conf. What's set in the universal_archs line? On Snow Leopard, it should read x86_64 i386; if it doesn't, set it to that and rebuild gettext and anything else you installed with the universal variant. If it already says x86_64 i386, then a likely explanation is that you migrated this MacPorts install to this Mac from Leopard or earlier and haven't rebuilt all ports.

comment:5 Changed 10 years ago by ryandesign (Ryan Schmidt)

Any word on this, tlax?

comment:6 Changed 10 years ago by tlax@…

Yes. The /opt/local/etc/macports/macports.conf had wrong universal_archs. Setting them to x85_64 i386 fixed this problem.

Thanks for the help.

comment:7 in reply to:  6 Changed 10 years ago by tlax@…

Replying to tlax@…:

Yes. The /opt/local/etc/macports/macports.conf had wrong universal_archs. Setting them to x85_64 i386 fixed this problem.

Correction: "x86_64 i386"

comment:8 Changed 10 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

Oh good, glad you got it working. If your macports.conf came from another machine, or from an earlier Mac OS X, there may be other settings that are not up to current standards; you may want to spend a moment comparing your macports.conf with the file macports.conf.default in the same directory to see what other changes you may want to adopt.

Note: See TracTickets for help on using tickets.