[MacPorts] #49151: glib2, glib2-devel: error: Universal builds not supported

[MacPorts]

#49151: glib2, glib2-devel: error: Universal builds not supported
---------------------------------+--------------------------
  Reporter:  andyk@…             |      Owner:  ryandesign@…
      Type:  defect              |     Status:  reopened
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:  2.3.4
Resolution:                      |   Keywords:
      Port:  glib2, glib2-devel  |
---------------------------------+--------------------------

Comment (by davalpi@…):

 Replying to [comment:14 ryandesign@…]:
 > The libxslt version of the problem was reported again in #49399 and an
 sqlite3 version of the problem was reported in #49398. Clearly something
 is still not right and I need to figure out why these additional libraries
 are being used.
 [[BR]]

 I report my experience because I try different things and I get very
 different behaviors.

 My target is to install wine. This port depend on glib2.

 I get the error " {{{file was built for x86_64 which is not the
 architecture being linked (i386):}}} " on sqlite3.

 My setup is : OSX (10.11.1 El Capitan ) and current XCode (xcodebuild
 -version -> Xcode 7.1 Build version 7B91b) - I do not have any JDK
 installed (I do not want one) but I have installed some latest JRE (jre-
 8u65-macosx-x64.dmg) from Oracle.

 I always start cleaning all  ({{{ sudo port -f uninstall installed ; sudo
 rm -rf /opt/local/var/macports/build/* ; sudo port selfupdate }}} ).

 === Install only wine - all clear ===

 If I install wine right after cleaning all, it works OK :
 {{{
 $ sudo port -f uninstall installed ; sudo rm -rf
 /opt/local/var/macports/build/* ; sudo port selfupdate
 . . .
 $ sudo port install wine
 --->  Computing dependencies for wine
 . . .
 --->  Extracting wine
 --->  Applying patches to wine
 --->  Configuring wine
 --->  Building wine
 --->  Staging wine into destroot
 --->  Installing wine @1.6.2_4
 --->  Activating wine @1.6.2_4
 --->  Cleaning wine
 --->  Updating database of binaries
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 }}}

 === Install wine after restoring other ports - all clear ===
 If I restore my previously installed port first, I get the error :

 {{{
 $ sudo port -f uninstall installed ; sudo rm -rf
 /opt/local/var/macports/build/* ; sudo port selfupdate
 . . .
 $ sudo ./restore_ports.tcl ports-installed-pre-el-capitan.txt
 . . .
 $ sudo port install wine
 --->  Computing dependencies for wine
 . . .
 Computing dependencies for glib2
 --->  Building glib2
 Error: org.macports.build for port glib2 returned: command execution
 failed
 ...
 $ cat
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glib2/glib2/main.log
 . . .
 :info:build ld: in '/opt/local/lib/libsqlite3.dylib', file was built for
 x86_64 which is not the architecture being linked (i386):
 /opt/local/lib/libsqlite3.dylib for architecture i386
 . . .
 }}}
 I have used the Migration procedure at
 https://trac.macports.org/wiki/Migratio.

 I'll attach to this tread {{{ports-installed-pre-el-capitan.txt}}}.

 This is the related list of requested ports: {{{ports-requested-pre-el-
 capitan.txt}}} I have used:
 {{{
 gnupg2
 gnutar
 mysql56
 pstree
 py27-pip
 py27-virtualenv
 py27-virtualenvwrapper
 python27
 rsync
 }}}
 Note that {{{sqlite3}}} is among the installed because {{{python27}}} (and
 maybe other) depend on it.

 The strangest behavior I observe is that even if {{{sqlite3}}} is
 installed in the restore_ports.tcl step, the {{{sudo port install wine}}}
 step is still trying to install it again .... I'm puzzled about this and I
 do not have saved full log about this but I can redo the steps and proved
 complete logs if is needed.

 === My conclusion ===

 It seem to me that a wild different behavior like this is worth to
 investigate more.

-- 
Ticket URL: <https://trac.macports.org/ticket/49151#comment:15>
MacPorts <https://www.macports.org/>
Ports system for OS X