Re: Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details)
Brad-Allisons-MacBook-Pro:~ ballison$ wget --tries=1 --timeout=10 www.macports.org/install.php --2013-06-08 04:03:23-- http://www.macports.org/install.php Resolving www.macports.org (www.macports.org)... 17.251.224.55 Connecting to www.macports.org (www.macports.org)|17.251.224.55|:80... failed: Operation timed out. Giving up. On Sat, Jun 8, 2013 at 4:00 AM, Brad Allison wrote: > 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) > ___ 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)
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) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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: > 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 >>> command: >>> http://pastebin.com/i4ZN6w1S >> >> This log says: >> >> :info:configure configure: error: C compiler cannot create executables >> :info:configure See `config.log' for more details. >> >> Seeing that config.log file might tell us more about why it failed. > > Any idea where I can find the config.log file? Yes, it is in the directory identified by the command: port work db46 >>> Sorry but it is not in that directory. >>> >>> 21:22:45 >>> felixdrud@Ares ~ : port work db46 >>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >>> >>> 21:22:50 >>> felixdrud@Ares ~ : cd >>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >>> >>> 21:22:57 >>> felixdrud@Ares >>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >>> : la >>> total 16 >>> drwxr-xr-x 6 macports admin 204 22 Okt 21:16 . >>> drwxr-xr-x 3 macports admin 102 22 Okt 21:16 .. >>> -rw-r--r-- 1 macports admin 1192 22 Okt 21:16 .CC_PRINT_OPTIONS >>> drwxr-xr-x 2 macports admin68 22 Okt 21:16 .home >>> -rw-r--r-- 1 macports admin 147 22 Okt 21:16 .macports.db46.state >>> drwxr-xr-x 71 macports admin 2414 27 Sep 2007 db-4.6.21 >>> >>> >>> Would it perhaps help if i completely removed Macports and reinstalled it? >>> Would that be a problem or something? >> I found it by searching. It was in the "port work >> db46"/db-4.6.21/build_unix/ directory. >> >> http://pastebin.com/WYfnjx21 > > The relevant error in the config.log appears to be: > > ld: library not found for -lcrt1.10.6.o > > Please verify: does the file /usr/lib/crt1.10.6.o exist? No it did not exist. > I suspect it does not, and that this is the cause of the problem, in which > case, uninstalling and reinstalling MacPorts will not help, because that file > should be provided by Xcode's command line tools. So as in our FAQ [1], the > error "C compiler cannot create executables" indicates that the Xcode command > line tools are not installed properly. > > [1] https://trac.macports.org/wiki/FAQ#missingxcode > > Since you're on Mountain Lion, I assume you have Xcode 4.5.1; if not, you > should update. Then open Xcode.app, go to the Preferences window, to the > Downloads section, and update or install the command line tools from there. I recently removed Xcode, by using some script provided by apple. I then reinstalled the newest version. The problem was that I was missing the command line tool. I installed it from Xcode preferences and everything is working fine now. I was able so reinstall db46 and a perl package that I was missing. Thank you very much for your time and help. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 "crt1.*"; "libcrt*" seems really off to me as well. >> > > Don't worry about it, apparently Apple's ld expanded the semantics of -l. Ah. Didn't R the FM. Thanks! Justin -- Justin C. Walker Director Institute for the Enhancement of the Director's Income -- Fame is fleeting, but obscurity just drags on and on. F&E ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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't worry about it, apparently Apple's ld expanded the semantics of -l. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix/linux, openafs, kerberos, infrastructure http://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 directories. Note > addition of prefix and suffixes. (Although I suppose Apple might have done > something interesting yet again to ld on Mountain Lion) AFAICT, 10.8 has only "crt1.*"; "libcrt*" seems really off to me as well. HTH Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- I want to die, peacefully in my sleep, like my grandfather; not screaming in terror, like his passengers. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 come before, such as: https://discussions.apple.com/thread/4155902 http://www.mac-forums.com/forums/os-x-development-darwin/174131-linker-cannot-find-libraries-do-they-exist.html > (Although I suppose Apple might have done something interesting yet again to > ld on Mountain Lion) The above posts were with Lion and Snow Leopard, so I don't think this is anything new in Mountain Lion. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 Apple might have done something interesting yet again to ld on Mountain Lion) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix/linux, openafs, kerberos, infrastructure http://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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: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 >> command: >> http://pastebin.com/i4ZN6w1S > > This log says: > > :info:configure configure: error: C compiler cannot create executables > :info:configure See `config.log' for more details. > > Seeing that config.log file might tell us more about why it failed. Any idea where I can find the config.log file? >>> >>> Yes, it is in the directory identified by the command: >>> >>> port work db46 >> Sorry but it is not in that directory. >> >> 21:22:45 >> felixdrud@Ares ~ : port work db46 >> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >> >> 21:22:50 >> felixdrud@Ares ~ : cd >> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >> >> 21:22:57 >> felixdrud@Ares >> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work >> : la >> total 16 >> drwxr-xr-x 6 macports admin 204 22 Okt 21:16 . >> drwxr-xr-x 3 macports admin 102 22 Okt 21:16 .. >> -rw-r--r-- 1 macports admin 1192 22 Okt 21:16 .CC_PRINT_OPTIONS >> drwxr-xr-x 2 macports admin68 22 Okt 21:16 .home >> -rw-r--r-- 1 macports admin 147 22 Okt 21:16 .macports.db46.state >> drwxr-xr-x 71 macports admin 2414 27 Sep 2007 db-4.6.21 >> >> >> Would it perhaps help if i completely removed Macports and reinstalled it? >> Would that be a problem or something? >> > I found it by searching. It was in the "port work db46"/db-4.6.21/build_unix/ > directory. > > http://pastebin.com/WYfnjx21 The relevant error in the config.log appears to be: ld: library not found for -lcrt1.10.6.o Please verify: does the file /usr/lib/crt1.10.6.o exist? I suspect it does not, and that this is the cause of the problem, in which case, uninstalling and reinstalling MacPorts will not help, because that file should be provided by Xcode's command line tools. So as in our FAQ [1], the error "C compiler cannot create executables" indicates that the Xcode command line tools are not installed properly. [1] https://trac.macports.org/wiki/FAQ#missingxcode Since you're on Mountain Lion, I assume you have Xcode 4.5.1; if not, you should update. Then open Xcode.app, go to the Preferences window, to the Downloads section, and update or install the command line tools from there. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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: > > > > > > > > > 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 > > > > > command: > > > > > http://pastebin.com/i4ZN6w1S > > > > > > > > > > > > > > > > > This log says: > > > > > > > > :info:configure configure: error: C compiler cannot create executables > > > > :info:configure See `config.log' for more details. > > > > > > > > Seeing that config.log file might tell us more about why it failed. > > > > > > Any idea where I can find the config.log file? > > > > Yes, it is in the directory identified by the command: > > > > port work db46 > Sorry but it is not in that directory. > > 21:22:45 > felixdrud@Ares ~ : port work db46 > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work > > 21:22:50 > felixdrud@Ares ~ : cd > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work > > 21:22:57 > felixdrud@Ares > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work > : la > total 16 > drwxr-xr-x 6 macports admin 204 22 Okt 21:16 . > drwxr-xr-x 3 macports admin 102 22 Okt 21:16 .. > -rw-r--r-- 1 macports admin 1192 22 Okt 21:16 .CC_PRINT_OPTIONS > drwxr-xr-x 2 macports admin68 22 Okt 21:16 .home > -rw-r--r-- 1 macports admin 147 22 Okt 21:16 .macports.db46.state > drwxr-xr-x 71 macports admin 2414 27 Sep 2007 db-4.6.21 > > > Would it perhaps help if i completely removed Macports and reinstalled it? > Would that be a problem or something? > I found it by searching. It was in the "port work db46"/db-4.6.21/build_unix/ directory. http://pastebin.com/WYfnjx21 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 install db46 > > > > > > > > I did this but received the following error, when executing the last > > > > command: > > > > http://pastebin.com/i4ZN6w1S > > > > > > > > > > > > > This log says: > > > > > > :info:configure configure: error: C compiler cannot create executables > > > :info:configure See `config.log' for more details. > > > > > > Seeing that config.log file might tell us more about why it failed. > > > > Any idea where I can find the config.log file? > > Yes, it is in the directory identified by the command: > > port work db46 Sorry but it is not in that directory. 21:22:45 felixdrud@Ares ~ : port work db46 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work 21:22:50 felixdrud@Ares ~ : cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work 21:22:57 felixdrud@Ares /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_db46/db46/work : la total 16 drwxr-xr-x 6 macports admin 204 22 Okt 21:16 . drwxr-xr-x 3 macports admin 102 22 Okt 21:16 .. -rw-r--r-- 1 macports admin 1192 22 Okt 21:16 .CC_PRINT_OPTIONS drwxr-xr-x 2 macports admin68 22 Okt 21:16 .home -rw-r--r-- 1 macports admin 147 22 Okt 21:16 .macports.db46.state drwxr-xr-x 71 macports admin 2414 27 Sep 2007 db-4.6.21 Would it perhaps help if i completely removed Macports and reinstalled it? Would that be a problem or something? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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 >>> command: >>> http://pastebin.com/i4ZN6w1S >> >> This log says: >> >> :info:configure configure: error: C compiler cannot create executables >> :info:configure See `config.log' for more details. >> >> Seeing that config.log file might tell us more about why it failed. > > Any idea where I can find the config.log file? Yes, it is in the directory identified by the command: port work db46 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
> On Oct 20, 2012, at 17:52, Felix Emil Drud wrote: > >> I was trying to install pkgconfig libao, by doing this: >> >> sudo port install pkgconfig libao >> Password: >> ---> Computing dependencies for pkgconfig >> ---> Dependencies to be installed: 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_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log >> Error: The following dependencies were not installed: libiconv gperf >> 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. > > "shell command failed" tells us almost nothing other than that "something" > went wrong. MacPorts runs shell commands all the time. To learn anything, we > must know *what* shell command failed, and with *what* error message. The > aforementioned main.log file might tell us more. > >> I tried searching for the error and found a mailing list archive where it >> said that i should try reinstalling db46: > > That's probably not relevant to your issue. > >> 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 command: >> http://pastebin.com/i4ZN6w1S > > This log says: > > :info:configure configure: error: C compiler cannot create executables > :info:configure See `config.log' for more details. > > Seeing that config.log file might tell us more about why it failed. Any idea where I can find the config.log file? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
On Oct 20, 2012, at 17:52, Felix Emil Drud wrote: > I was trying to install pkgconfig libao, by doing this: > > sudo port install pkgconfig libao > Password: > ---> Computing dependencies for pkgconfig > ---> Dependencies to be installed: 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_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log > Error: The following dependencies were not installed: libiconv gperf > 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. "shell command failed" tells us almost nothing other than that "something" went wrong. MacPorts runs shell commands all the time. To learn anything, we must know *what* shell command failed, and with *what* error message. The aforementioned main.log file might tell us more. > I tried searching for the error and found a mailing list archive where it > said that i should try reinstalling db46: That's probably not relevant to your issue. > 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 command: > http://pastebin.com/i4ZN6w1S This log says: :info:configure configure: error: C compiler cannot create executables :info:configure See `config.log' for more details. Seeing that config.log file might tell us more about why it failed. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
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. October 2012 at 01.01, Jeremy Lavergne wrote: > > :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 mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: shell command failed
> :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 mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
shell command failed
Hello, I was trying to install pkgconfig libao, by doing this: sudo port install pkgconfig libao Password: ---> Computing dependencies for pkgconfig ---> Dependencies to be installed: 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_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/main.log Error: The following dependencies were not installed: libiconv gperf 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 where it said that i should try reinstalling db46: 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 command: http://pastebin.com/i4ZN6w1S Does anyone know how i can solve this issue? Thank you very much for your time Regards, -- Felix Emil Drud "Stay hungry, stay foolish." -Whole Earth Catalog ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error: Target org.macports.build returned: shell command failed (see log for details)
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 problem everybody else is experiencing building the latest glib2: https://trac.macports.org/ticket/32204 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.build returned: shell command failed (see log for details)
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 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: xorg-libxcb: shell command failed
Does it look similar to https://trac.macports.org/ticket/26418 ? Thanks, Kastus On Oct 6, 2011, at 10:09 AM, Zhong Ren wrote: 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 , 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/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. And please clean and try again before doing so. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: xorg-libxcb: shell command failed
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 , 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/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. > >And please clean and try again before doing so. > > > ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: xorg-libxcb: shell command failed
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_ports_x11_xorg-libxcb/xorg-libxcb/main.log > > Please post the log somewhere. And please clean and try again before doing so. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: xorg-libxcb: shell command failed
> 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. smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
xorg-libxcb: shell command failed
Hi, I need to install or upgrade xorg-libxcb because some other packages depend on it. I am stuck here for more than a week now. Is there a way to get around this? Can I use python26 and how? Any help is appreciated. Please see the error message below. renz@ounce.local:~ % sudo port 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/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libxcb/xorg-libxcb/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> Zhong Ren ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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 > another, and following the instructions in the link below resolved the issue. Great, glad you got it working. (Cc'ing the list on this response so everyone knows it's resolved.) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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: >> >> configure: error: iconv support requested, but not found > > that's odd. > > you can probably do the same with iconv that you did with db46 (uninstall, > clean, reinstall) and then clean/upgrade apr-util again. > > Did you by any chance migrate your macports installation from an older > machine to your current one? If so, you really need to follow the migration > instructions (https://trac.macports.org/wiki/Migration) Yes, it looks like a typical Migration situation. The real error message would probably have been in the config.log. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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 found that's odd. you can probably do the same with iconv that you did with db46 (uninstall, clean, reinstall) and then clean/upgrade apr-util again. Did you by any chance migrate your macports installation from an older machine to your current one? If so, you really need to follow the migration instructions (https://trac.macports.org/wiki/Migration) -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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 found > shell command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_apr-util/work/apr-util-1.3.10" > && ./configure --prefix=/opt/local --with-apr=/opt/local/bin/apr-1-config > --with-expat=/opt/local --with-iconv=/opt/local > --with-berkeley-db=/opt/local/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 for > details) > while executing > "$procedure $targetname" > Warning: the following items did not execute (for apr-util): > org.macports.destroot org.macports.configure org.macports.build > Log for apr-util is at: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_apr-util/main.log > DEBUG: couldn't open > "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": > no such file or directory > while executing > "open [file join $dir tclIndex]" > Error: Unable to upgrade port: 1 What should I try next? On 13 April 2011 16:19, Daniel J. Luke wrote: > 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 /opt/local/include and > /opt/local/lib/db46... > :info:configure checking db46/db.h usability... yes > :info:configure checking db46/db.h presence... yes > :info:configure checking for db46/db.h... yes > > So, perhaps something is wrong with your macports-installed db46? > > You could look and see if /opt/local/lib/db46/libdb-4.6.dylib exists and is > the right architecture for your machine. > > Mine looks like this: > % file /opt/local/lib/db46/libdb-4.6.dylib > /opt/local/lib/db46/libdb-4.6.dylib: Mach-O universal binary with 2 > architectures > /opt/local/lib/db46/libdb-4.6.dylib (for architecture i386):Mach-O > dynamically linked shared library i386 > /opt/local/lib/db46/libdb-4.6.dylib (for architecture x86_64): Mach-O > 64-bit dynamically linked shared library x86_64 > > > The log is attached to this email. What is the best way to go about > resolving this? I'm a relative newcomer to Macports. > > A quick fix might be to uninstall and reinstall db46: > > sudo port -f uninstall db46 > sudo port clean --all db46 > sudo port install db46 > > and then try cleaning and upgrading apr-util again > > sudo port clean apr-util > sudo port -dv upgrade apr-util > > -- > Daniel J. Luke > ++ > | * dl...@geeklair.net * | > | *-- http://www.geeklair.net -* | > ++ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > ++ > > > > ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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 /opt/local/include and /opt/local/lib/db46... :info:configure checking db46/db.h usability... yes :info:configure checking db46/db.h presence... yes :info:configure checking for db46/db.h... yes So, perhaps something is wrong with your macports-installed db46? You could look and see if /opt/local/lib/db46/libdb-4.6.dylib exists and is the right architecture for your machine. Mine looks like this: % file /opt/local/lib/db46/libdb-4.6.dylib /opt/local/lib/db46/libdb-4.6.dylib: Mach-O universal binary with 2 architectures /opt/local/lib/db46/libdb-4.6.dylib (for architecture i386):Mach-O dynamically linked shared library i386 /opt/local/lib/db46/libdb-4.6.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 > The log is attached to this email. What is the best way to go about resolving > this? I'm a relative newcomer to Macports. A quick fix might be to uninstall and reinstall db46: sudo port -f uninstall db46 sudo port clean --all db46 sudo port install db46 and then try cleaning and upgrading apr-util again sudo port clean apr-util sudo port -dv upgrade apr-util -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
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) The log is attached to this email. What is the best way to go about resolving this? I'm a relative newcomer to Macports. Thanks, --Jim -- My IM and Skype details are at http://state68.com/contact main.log Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Evince Upgrade Error shell command failed
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 command failed (see log for > details) > Log for evince is at: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/main.log We would need to see the contents of that log file to have any idea what went wrong. Perhaps it is this problem? If so, there is a patch attached that you could try. https://trac.macports.org/ticket/28264 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Evince Upgrade Error shell command failed
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/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/main.log Error: Unable to upgrade port: 1 To report a bug, see <http://guide.macports.org/#project.tickets> You have new mail in /var/mail/jasper jaspersmbp:~ jasper$ tail /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/main.log :info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/work/evince-2.30.3" && /usr/bin/make -j2 all " returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for evince): org.macports.destroot org.macports.build :notice:build Log for evince is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/main.log ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: "shell command failed": for multiple ports on 1.9.1
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 same "shell command failed" error also for lame, > libmad and wine. > > "shell command failed" doesn't tell us anything; we need to know what shell > command failed and with what error message. I've added a message to your > Trac ticket about the specific error you mentioned there. If you have other > errors to report with other ports, please do so. > > > Sorry for not being more clear. I simply assumed the "shell command failed" always had the same reason. Your additional info to the ticket mentioned here<http://trac.macports.org/ticket/25581>was indeed the solution for that problem with dbus-glib, but not for the others. I will collect and analyze the log files, search the tracker and I will file tickets. Either with a solution or for an open bug. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: "shell command failed": for multiple ports on 1.9.1
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 also for lame, > libmad and wine. "shell command failed" doesn't tell us anything; we need to know what shell command failed and with what error message. I've added a message to your Trac ticket about the specific error you mentioned there. If you have other errors to report with other ports, please do so. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
"shell command failed": for multiple ports on 1.9.1
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, I now get the same "shell command failed" error also for lame, libmad and wine. I can off course submit more bug tickets but I first want to know whether it can be a configuration issue on my Mac (Macbook Pro, OSX 10.5.8, Macports 1.9.1). It only happens for universal builds. If I use "sudo port install -universal" the ports are built correctly for i386. Then I decided to do a "sudo port uninstall installed", and to be sure followed by a "sudo port clean all" (sigh). Then I restarted building the whole bunch again, but with the exact same results for the above mentioned ports dbus-glib, lame, libmad and wine. (and maybe many more which I didn't touch yet). relevant parts from my /opt/local/etc/macports/macports.conf: # MACOSX_DEPLOYMENT_TARGET #universal_target 10.4 #universal_target10.5 # the SDK "sysroot" to use #universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk #universal_sysroot /Developer/SDKs/MacOSX10.5.sdk # machine architectures universal_archs i386 ppc I'm on intel (see above) so I put i386 as first architecture. Entries of my /opt/local/etc/macports/variants.conf: +universal +no_x11 +quartz ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
