Ryan Schmidt wrote:
On Nov 4, 2010, at 17:47, John B Brown wrote:
I've found that this sort of corruption can only be cured with;
sudo port -f uninstall installed
If you are really lucky, the garbage will be greatly reduced. For full
directions visit:
http://guide.macports.org/chunked/installing.macports.uninstalling.html
Then, after a reinstall of port, look for xfig dependencies prior to
installing it. Try the dependencies one at a time; it's easier to reverse
errors singly.
Macports is a buggy software scheme, as buggy as possible, but one can
survive the bugs by exercising caution and care. Caveat emptor.
John, the advice to uninstall and reinstall ports may be exactly what is needed
(Joel, see below for more on this), but you are out of line with your last
statement that MacPorts is as buggy as possible. MacPorts works well, but
though we would like it to be a user-friendly tool, today it is more of a pro
user's tool. Building software is actually a complicated thing, when you think
about all the variables involved, and it's important to understand some of
what's going on under the hood in MacPorts in order to get the most out of it
and know how to resolve issues that may arise. If you are not happy with
MacPorts you are welcome to help improve it or to uninstall it, but I don't
believe the attitude is a constructive way to interact with other users who are
just asking for help.
Since when has rendering an honest opinion been unacceptable? As you
say, macports is more for professionals than GUI users, but it exhibits
bugs constantly. I accept them, deal with them as rapidly as possible,
and have learned many methods to execute my dealings with "bugs." That's
why I use TUG for TeX.
Joel Friedman wrote:
Hi Everyone,
I have a MacBookPro running OS X 10.6.4 . I bought it a month or two ago,
and I believe it came with 10.6.
Yesterday I ran
sudo port install xfig
and had serious problems. I don't have the orignal message, but when I
rerun the install xfig I get--
---> Staging netpbm into destroot
Error: Target org.macports.destroot returned: shell command failed
Log for netpbm is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_netpbm/main.log
Error: The following dependencies failed to build: transfig netpbm xorg-libXi
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
The log for netpbm includes:
:info:destroot dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
:info:destroot Referenced from: /opt/local/bin/date
:info:destroot Reason: no suitable image found. Did find:
:info:destroot /opt/local/lib/libintl.8.dylib: mach-o, but wrong architecture
Now when I try to run /opt/local/bin/date I get:
j...@mac_etc[533]: /opt/local/bin/date
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
Referenced from: /opt/local/bin/date
Reason: no suitable image found. Did find:
/opt/local/lib/libintl.8.dylib: mach-o, but wrong architecture
Trace/BPT trap
I've tried uninstalling, cleaning, getting the latest Xcode, and again
installing xfig to no avail.
Beforehand /opt/local/bin/date worked fine.
Any ideas? I would greatly appreciate any help.
Thanks.
Joel
Joel, it sounds like your /opt/local/bin/date command is not of the same architecture as your /opt/local/lib/libintl.8.dylib library. A common reason for this to occur is if you migrated a previous MacPorts installation from another computer running 10.5 or earlier to your new MacBook Pro with 10.6, for example by answering in the affirmative when setting up your new MacBook Pro when it asked you if you wanted to transfer data from another computer. (This is Apple's "Migration Assistant".)
Perhaps you could check what architecture /opt/local/bin/date and
/opt/local/lib/libintl.8.dylib are. The command to do so is:
lipo -info /opt/local/bin/date /opt/local/lib/libintl.8.dylib
The correct answer for a system with Mac OS X 10.6 should include "x86_64" on
each line; if either does not, then the situation I described above is likely.
You should also check your /opt/local/etc/macports/macports.conf, specifically
for the values of build_arch and universal_archs (what are they currently?),
but other values are important to check as well. Compare each line of
macports.conf with the corresponding line of macports.conf.default in the same
directory. Where lines differ, copy the line(s) from macports.conf.default to
macports.conf, unless you have a specific reason for having made a change in
macports.conf. In the end, build_arch should be x86_64 and universal_archs
should be the combination of i386 and x86_64.
If you did in fact migrate an older MacPorts installation (likely of a
different architecture) to this machine, then you will need to clean that up by
uninstalling all ports and then reinstalling the ones you want. This is what
John was alluding to above and is explained in more detail in our Migration
page:
http://trac.macports.org/wiki/Migration
Shalom,
John B. Brown.
[[email protected]]
358 High Street,
Buffalo, Wyoming
82834
"Freedom is not worth having if it does not include
the freedom to make mistakes" Mahatma Gandhi
"If any question why we died, tell them,
because our fathers lied." Rudyard Kipling
"A man who does not know the truth is just an idiot
but a man who knows the truth and calls it a lie
is a crook." Bertolt Brecht
"I wonder whether the world is being run
by smart people who are putting us on
or by imbeciles who really mean it." Mark Twain
1-307-684-9068
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
