Re: Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)

2013-06-08 Thread Brad Allison
sources: shell command failed (see log for details) > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)

2013-06-08 Thread Brad Allison
Brad-Allisons-MacBook-Pro:~ ballison$ sudo port selfupdate ---> Updating MacPorts base sources using rsync Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details) ___ macpo

Re: shell command failed

2012-10-24 Thread Felix Drud
Den 23/10/2012 kl. 18.04 skrev Ryan Schmidt : > On Oct 22, 2012, at 14:28, Felix Emil Drud wrote: >> On Monday den 22. October 2012 at 21.24, Felix Emil Drud wrote: >>> On Monday den 22. October 2012 at 06.24, Ryan Schmidt wrote: On Oct 21, 2012, at 23:06, Felix Drud wrote: > Ry

Re: shell command failed

2012-10-24 Thread Justin C. Walker
On Oct 24, 2012, at 10:11 , Brandon Allbery wrote: > On Wed, Oct 24, 2012 at 1:08 PM, Justin C. Walker wrote: > >>> This looks broken to me; "-lcrt1.10.6.o" will expand to a search for >>> "libcrt1.10.6.o.dylib" and "libcrt1.10.6.o.a" in various directories. >> Note >> >> AFAICT, 10.8 has only

Re: shell command failed

2012-10-24 Thread Brandon Allbery
On Wed, Oct 24, 2012 at 1:08 PM, Justin C. Walker wrote: > > This looks broken to me; "-lcrt1.10.6.o" will expand to a search for > > "libcrt1.10.6.o.dylib" and "libcrt1.10.6.o.a" in various directories. > Note > > AFAICT, 10.8 has only "crt1.*"; "libcrt*" seems really off to me as well. > Don'

Re: shell command failed

2012-10-24 Thread Justin C. Walker
On Oct 23, 2012, at 09:07 , Brandon Allbery wrote: > On Tue, Oct 23, 2012 at 12:04 PM, Ryan Schmidt wrote: > >> ld: library not found for -lcrt1.10.6.o >> > > This looks broken to me; "-lcrt1.10.6.o" will expand to a search for > "libcrt1.10.6.o.dylib" and "libcrt1.10.6.o.a" in various directo

Re: shell command failed

2012-10-23 Thread Ryan Schmidt
On Oct 23, 2012, at 11:07, Brandon Allbery wrote: > This looks broken to me; "-lcrt1.10.6.o" will expand to a search for > "libcrt1.10.6.o.dylib" and "libcrt1.10.6.o.a" in various directories. Note > addition of prefix and suffixes. That's true, but I was basing my answer on others that have

Re: shell command failed

2012-10-23 Thread Brandon Allbery
On Tue, Oct 23, 2012 at 12:04 PM, Ryan Schmidt wrote: > ld: library not found for -lcrt1.10.6.o > This looks broken to me; "-lcrt1.10.6.o" will expand to a search for "libcrt1.10.6.o.dylib" and "libcrt1.10.6.o.a" in various directories. Note addition of prefix and suffixes. (Although I suppose

Re: shell command failed

2012-10-23 Thread Ryan Schmidt
On Oct 22, 2012, at 14:28, Felix Emil Drud wrote: > On Monday den 22. October 2012 at 21.24, Felix Emil Drud wrote: >> On Monday den 22. October 2012 at 06.24, Ryan Schmidt wrote: >>> >>> On Oct 21, 2012, at 23:06, Felix Drud wrote: >>> Ryan Schmidt wrote: > On Oct 20, 2012, at 17:

Re: shell command failed

2012-10-22 Thread Felix Emil Drud
On Monday den 22. October 2012 at 21.24, Felix Emil Drud wrote: > On Monday den 22. October 2012 at 06.24, Ryan Schmidt wrote: > > > > On Oct 21, 2012, at 23:06, Felix Drud wrote: > > > > > Ryan Schmidt wrote: > > > > > > > On Oct 20, 2012, at 17:52, Felix Emil Drud wrote: > > > > > > > > > sud

Re: shell command failed

2012-10-22 Thread Felix Emil Drud
On Monday den 22. October 2012 at 06.24, Ryan Schmidt wrote: > > On Oct 21, 2012, at 23:06, Felix Drud wrote: > > > Ryan Schmidt wrote: > > > > > On Oct 20, 2012, at 17:52, Felix Emil Drud wrote: > > > > > > > sudo port -f uninstall db46 > > > > sudo port clean --all db46 > > > > sudo port inst

Re: shell command failed

2012-10-21 Thread Ryan Schmidt
On Oct 21, 2012, at 23:06, Felix Drud wrote: > Ryan Schmidt wrote: > >> On Oct 20, 2012, at 17:52, Felix Emil Drud wrote: >> >>> sudo port -f uninstall db46 >>> sudo port clean --all db46 >>> sudo port install db46 >>> >>> I did this but received the following error, when executing the last

Re: shell command failed

2012-10-21 Thread Felix Drud
alled: libiconv gperf >> ---> Configuring gperf >> Error: Target org.macports.configure returned: configure failure: shell >> command failed (see log for details) >> Error: Failed to install gperf >> Log for gperf is at: >> /opt/local/var/macports/logs/_opt

Re: shell command failed

2012-10-21 Thread Ryan Schmidt
gt; Configuring gperf > Error: Target org.macports.configure returned: configure failure: shell > command failed (see log for details) > Error: Failed to install gperf > Log for gperf is at: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarb

Re: shell command failed

2012-10-20 Thread Felix Emil Drud
Thank you for your answer. I get this: i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) (Sorry, forgot to reply to all - i.e. cc the mailing list). -- Felix Emil Drud "Stay hungry, stay foolish." -Whole Earth Catalog On Sunday den 21. Octo

Re: shell command failed

2012-10-20 Thread Jeremy Lavergne
> :info:configure configure: error: C compiler cannot create executables The problem appears to be with the compiler (llvm). What happens when you run: /Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 --version ___ macports-users mail

shell command failed

2012-10-20 Thread Felix Emil Drud
erf Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> I keep getting the "shell command failed" error whenever i try to install anything, using macports. I tried searching for the error and found a mailing list archive whe

Re: Error: Target org.macports.build returned: shell command failed (see log for details)

2011-11-23 Thread Ryan Schmidt
On Nov 23, 2011, at 14:55, barry holland wrote: > Error: Target org.macports.build returned: shell command failed (see log for > details) That means "something failed during the build phase", so not very useful. > The contents of your log shows it's the same p

Re: Error: Target org.macports.build returned: shell command failed (see log for details)

2011-11-23 Thread Ryan Schmidt
On Nov 23, 2011, at 15:19, Ryan Schmidt wrote: > The contents of your log shows it's the same problem everybody else is > experiencing building the latest glib2: > > https://trac.macports.org/ticket/32204 Sorry, pasted wrong link; should have been: https://trac.macports.org/ticket/32185 __

Re: xorg-libxcb: shell command failed

2011-10-07 Thread Kastus Shchuka
: Ryan Schmidt Subject: Re: xorg-libxcb: shell command failed To: r...@uchicago.edu Cc: Jeremy Lavergne , MacPorts Users > On Oct 5, 2011, at 21:54, Jeremy Lavergne wrote: Error: Target org.macports.build returned: shell command failed (see log for details) Log for xorg-libxcb is at: /opt/lo

Re: xorg-libxcb: shell command failed

2011-10-06 Thread Zhong Ren
Clean did not do any good. The log is at https://trac.macports.org/ticket/31439 Zhong Ren Original message >Date: Wed, 5 Oct 2011 23:03:02 -0500 >From: Ryan Schmidt >Subject: Re: xorg-libxcb: shell command failed >To: r...@uchicago.edu >Cc: Jeremy Lavergne ,

Re: xorg-libxcb: shell command failed

2011-10-05 Thread Ryan Schmidt
On Oct 5, 2011, at 21:54, Jeremy Lavergne wrote: >> Error: Target org.macports.build returned: shell command failed (see log for >> details) >> Log for xorg-libxcb is at: >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_po

Re: xorg-libxcb: shell command failed

2011-10-05 Thread Jeremy Lavergne
> Error: Target org.macports.build returned: shell command failed (see log for > details) > Log for xorg-libxcb is at: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libxcb/xorg-libxcb/main.log Please post the log somewhere.

xorg-libxcb: shell command failed

2011-10-05 Thread Zhong Ren
install xorg-libxcb +python27+universal ---> Computing dependencies for xorg-libxcb ---> Building xorg-libxcb Error: Target org.macports.build returned: shell command failed (see log for details) Log for xorg-libxcb is at: /opt/local/var/macport

Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-17 Thread Ryan Schmidt
On Apr 17, 2011, at 11:38, James Benstead wrote: > On 14 April 2011 00:31, Ryan Schmidt wrote: > >> Yes, it looks like a typical Migration situation. The real error message >> would probably have been in the config.log. > > Thanks guys - I had migrated the Macports installation from one Mac to

Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-13 Thread Ryan Schmidt
On Apr 13, 2011, at 11:14, Daniel J. Luke wrote: > On Apr 13, 2011, at 11:36 AM, James Benstead wrote: >> >> Thanks for the quick - and really helpful response. I've worked through this >> but the final command, >> >> sudo port -dv upgrade apr-util >> >> Returned the following error message:

Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-13 Thread Daniel J. Luke
On Apr 13, 2011, at 11:36 AM, James Benstead wrote: > > Thanks for the quick - and really helpful response. I've worked through this > but the final command, > > sudo port -dv upgrade apr-util > > Returned the following error message: > > configure: error: iconv support requested, but not foun

Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-13 Thread James Benstead
include:/opt/local/lib/db46 --without-mysql > --without-pgsql --with-sqlite3=/opt/local " returned error 1 > Error: Target org.macports.configure returned: configure failure: shell > command failed (see log for details) > DEBUG: Backtrace: configure failure: shell command failed (see log fo

Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-13 Thread Daniel J. Luke
On Apr 13, 2011, at 11:05 AM, James Benstead wrote: > > From your just-posted main.log, it looks like apr-util can't load the > dylib that should be installed with db46 > (/opt/local/lib/db46/libdb-4.6.dylib) This is from the log you attached: :info:configure checking for Berkeley DB 4.6 in /op

Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)

2011-04-13 Thread James Benstead
I (incorrectly) posted a ticket at https://trac.macports.org/ticket/29114and was redirected here, before receiving the following feedback: >From your just-posted main.log, it looks like apr-util can't load the > dylib that should be installed with db46 > (/opt/local/lib/db46/libdb-4.6.dylib) T

Re: Evince Upgrade Error shell command failed

2011-02-08 Thread Ryan Schmidt
On Feb 8, 2011, at 07:33, Jasper Frumau wrote: > Wanted to to an upgrade and it failed with evince: > > $ sudo port upgrade installed > Password: > ---> Computing dependencies for evince > ---> Building evince > Error: Target org.macports.build returned: shell

Evince Upgrade Error shell command failed

2011-02-08 Thread Jasper Frumau
Wanted to to an upgrade and it failed with evince: $ sudo port upgrade installed Password: ---> Computing dependencies for evince ---> Building evince Error: Target org.macports.build returned: shell command failed (see log for details) Log for evince is at: /opt/local/var/macport

Re: "shell command failed": for multiple ports on 1.9.1

2010-07-09 Thread Harry van der Wolf
2010/7/9 Ryan Schmidt > > On Jul 9, 2010, at 09:48, Harry van der Wolf wrote: > > > I received this "shell command failed" for dbus-glib (0.86_1) and I filed > a ticket for it at the macports trac (see here) as it also failed on 1.8.1. > > However, I now get the

Re: "shell command failed": for multiple ports on 1.9.1

2010-07-09 Thread Ryan Schmidt
On Jul 9, 2010, at 09:48, Harry van der Wolf wrote: > I received this "shell command failed" for dbus-glib (0.86_1) and I filed a > ticket for it at the macports trac (see here) as it also failed on 1.8.1. > However, I now get the same "shell command failed" error

"shell command failed": for multiple ports on 1.9.1

2010-07-09 Thread Harry van der Wolf
Hi, I upgraded to 1.9.1 yesterday and tried to do an "upgrade outdated". I received this "shell command failed" for dbus-glib (0.86_1) and I filed a ticket for it at the macports trac (see here<http://trac.macports.org/ticket/25581>) as it also failed on 1.8.1. However,