#46371 closed defect (worksforme)
gconf missing gsed as build dep?
Reported by: | jpo@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | haspatch | Cc: | kurthindenburg (Kurt Hindenburg) |
Port: | gconf |
Description (last modified by mf2k (Frank Schima))
From the failed build log:
:info:build CCLD libgconf-2.la :info:build ../libtool: line 861: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 867: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 2522: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 2522: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 7883: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 1316: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 8968: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 5014: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 5326: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 5327: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 9457: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 9881: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 9882: /opt/local/bin/gsed: No such file or directory :info:build ../libtool: line 9883: /opt/local/bin/gsed: No such file or directory
Not sure if this is correct or not, but it fixed the build for me.
Attachments (1)
Change History (9)
Changed 10 years ago by jpo@…
Attachment: | Portfile.patch added |
---|
comment:1 Changed 10 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|
comment:2 Changed 10 years ago by mf2k (Frank Schima)
comment:3 Changed 10 years ago by larryv (Lawrence Velázquez)
This should not be necessary. Can you please clean gconf
and try building again, and then attach the complete main.log
? Also, what version of the libtool
port do you have installed?
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
This kind of problem usually occurs when you upgrade from OS X 10.8 or earlier to OS X 10.9 or later and do not uninstall and reinstall all ports as per the migration instructions. It has to do with the fact that as of OS X 10.9 we are no longer using .la files in MacPorts, and you still have .la file on your system from an older OS X version's MacPorts installation.
comment:5 Changed 10 years ago by jpo@…
I can confirm that a clean install of macports 2.3.3 on a clean install of osx 10.10 does not exhibit this behavior, so I guess just close this ticket.
I upgraded from 10.9 (which was a completely clean install to an empty drive, copying nothing over) to 10.10, and just did mv /opt/local /opt/old-macports && rm -rf /Applications/MacPorts /Library/Launch{Agents,Daemons}/org.macports.*
since I wanted to keep at least my old /opt/local/etc and /opt/local/var around in case I wanted to reference them later, and then installed macports 2.3.3 from the 10.10 pkg, and then started with a port install
of my previous port -q echo requested
, then added back my local ports repo to my macports.conf (which contained only Portfiles and patches, no work dirs or anything, and no ports in any part of the full dependency tree of gconf).
comment:6 Changed 10 years ago by jpo@…
And for whatever reason I can no longer reproduce the problem either, so yeah, close this. Sorry for the noise.
comment:7 Changed 10 years ago by mf2k (Frank Schima)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Thanks. In the future, please use WikiFormatting.