Re: New Macports using trying to install octave
On Nov 9, 2007, at 11:36, Jackson Myers wrote:
On Nov 9, 2007, at 4:42 AM, Ryan Schmidt wrote:
On Nov 8, 2007, at 16:52, Jackson Myers wrote:
I am new to Macports (but I have some Unix/Darwin experience and I have used Fink before). I am trying to install Octave on Leopard and not having much luck. The following is an error I got on my first attempt. Can anybody decipher this and tell me how to make it work? thanks, -Jax
I think it means that you have a PowerPC Mac, and the octave port requests gcc40 on PowerPC machines, and gcc40 apparently won't build on Leopard anymore. We've had at least one other report of this that I recall. There's an open bug requesting that this be changed to use gcc42. There's a patch attached to the ticket. You could try the patch and see if it helps:
http://trac.macports.org/projects/macports/ticket/12144
There's also an open request to update the port to the current version:
http://trac.macports.org/projects/macports/ticket/12937
The port's maintainer is busy with other things right now so he hasn't had a chance to look at these tickets. But if you try the patches and they fix the problem for you, someone else could commit them.
Thanks for the info. I'll give it a try. Just a quick question though: How do I apply that patch?
Whoops, it looks like my patch in ticket 12144 has rotted. I'm attaching an updated patch to the ticket. So now you can: sudo port clean --work octave cd `port dir octave` sudo patch -p0 < ~/Desktop/octave-gcc42-2.diff sudo port install octave The patch will disappear the next time you do a "sudo port selfupdate" or "sudo port sync". I don't use octave and I haven't tried the patch myself so if you run into more problems please let us know.
On Nov 9, 2007, at 2:18 PM, Ryan Schmidt wrote:
On Nov 9, 2007, at 11:36, Jackson Myers wrote:
On Nov 9, 2007, at 4:42 AM, Ryan Schmidt wrote:
On Nov 8, 2007, at 16:52, Jackson Myers wrote:
Whoops, it looks like my patch in ticket 12144 has rotted. I'm attaching an updated patch to the ticket.
So now you can:
sudo port clean --work octave cd `port dir octave` sudo patch -p0 < ~/Desktop/octave-gcc42-2.diff sudo port install octave
The patch will disappear the next time you do a "sudo port selfupdate" or "sudo port sync".
I don't use octave and I haven't tried the patch myself so if you run into more problems please let us know.
This patch was insufficient for getting the install to work. I get the failure: ---> Building octave with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_math_octave/work/octave-2.9.9" && make all " returned error 2 Command output: ls: *.cc: No such file or directory make -C tests all making PKG_ADD ls: *.cc: No such file or directory make -C strings all making PKG_ADD ls: *.cc: No such file or directory make -C testfun all make[3]: Nothing to be done for `all'. make -C time all making PKG_ADD ls: *.cc: No such file or directory make -C doc all make -C faq all make[3]: Nothing to be done for `all'. make -C interpreter all make -C ../../src DOCSTRINGS making defaults.h from defaults.h.in defaults.h is unchanged making oct-conf.h from oct-conf.h.in oct-conf.h is unchanged make[4]: `DOCSTRINGS' is up to date. make -C ../../scripts DOCSTRINGS make[4]: `DOCSTRINGS' is up to date. making arith.texi from arith.txi /bin/sh: line 1: 1894 Segmentation fault ./munge-texi -d ../../ src/DOCSTRINGS -d ../../scripts/DOCSTRINGS < arith.txi > arith.texi.t make[3]: *** [arith.texi] Error 139 make[2]: *** [interpreter] Error 2 make[1]: *** [doc] Error 2 make: *** [all] Error 2 Error: Status 1 encountered during processing. with a crash dialogue box that pops up containing "The application munge-texi quit unexpectedly" (Report follows) Process: munge-texi [1894] Path: munge-texi Identifier: munge-texi Version: ??? (???) Code Type: X86 (Native) Parent Process: sh [1893] Date/Time: 2007-11-16 08:57:04.498 -0500 OS Version: Mac OS X 10.5.1 (9B18) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: 0x000000000000000d, 0x0000000000000000 Crashed Thread: 0 Thread 0 Crashed: 0 dyld 0x8fe18aa2 misaligned_stack_error + 0 1 libstdc++.6.dylib 0x00106763 std::_Rb_tree_insert_and_rebalance(bool, std::_Rb_tree_node_base*, std::_Rb_tree_node_base*, std::_Rb_tree_node_base&) + 243 2 munge-texi 0x000044c7 std::_Rb_tree<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
, std::_Select1st<std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
, std::less<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
::_M_insert(std::_Rb_tree_node_base*, std::_Rb_tree_node_base*, std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) + 119 3 munge-texi 0x00004968 std::_Rb_tree<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> > , std::_Select1st<std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> > , std::less<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
::_M_insert_unique (std::_Rb_tree_iterator<std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
, std::pair<std::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > const&) + 536 4 munge-texi 0x000032c7 process_doc_file(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 1159 5 munge-texi 0x0000388e main + 94 6 munge-texi 0x000025ec _start + 210 7 munge-texi 0x00002519 start + 41
Thread 0 crashed with X86 Thread State (32-bit): eax: 0x0019495b ebx: 0x00004461 ecx: 0x00000000 edx: 0x0000537c edi: 0x002002f0 esi: 0x00200310 ebp: 0xbffff54c esp: 0xbffff4e4 ss: 0x0000001f efl: 0x00010282 eip: 0x8fe18aa2 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0xffe2a750 Binary Images: 0x1000 - 0x4fff +munge-texi ??? (???) /opt/local/var/macports/ build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_math_octave/work/octave-2.9.9/doc/ interpreter/munge-texi 0x27000 - 0x2efed +libgcc_s.1.dylib ??? (???) /opt/local/lib/ gcc42/libgcc_s.1.dylib 0xee000 - 0x17efe7 +libstdc++.6.dylib ??? (???) /opt/local/lib/ gcc42/libstdc++.6.dylib 0x8fe00000 - 0x8fe2d883 dyld 95.3 (???) <81592e798780564b5d46b988f7ee1a6a> /usr/lib/dyld 0x93cf0000 - 0x93e4afe3 libSystem.B.dylib ??? (???) <8ecc83dc0399be3946f7a46e88cf4bbb> /usr/lib/libSystem.B.dylib 0x96d6c000 - 0x96d6dfef libmathCommon.A.dylib ??? (???) /usr/lib/ system/libmathCommon.A.dylib 0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/ libSystem.B.dylib Well, I'm sure this makes sense to someone, but I'm certainly not that someone. Best, Joe
On Nov 16, 2007, at 08:00, Joseph C. Slater PE, PhD wrote:
On Nov 9, 2007, at 2:18 PM, Ryan Schmidt wrote:
Whoops, it looks like my patch in ticket 12144 has rotted. I'm attaching an updated patch to the ticket.
So now you can:
sudo port clean --work octave cd `port dir octave` sudo patch -p0 < ~/Desktop/octave-gcc42-2.diff sudo port install octave
The patch will disappear the next time you do a "sudo port selfupdate" or "sudo port sync".
I don't use octave and I haven't tried the patch myself so if you run into more problems please let us know.
This patch was insufficient for getting the install to work. I get the failure:
---> Building octave with target all Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_math_ octave/work/octave-2.9.9" && make all " returned error 2 Command output: ls: *.cc: No such file or directory
[snip] But at least you got past the initial problem Jackson had, which was that gcc40 wouldn't build. Now, you have successfully built gcc42, it seems, and are having problems with octave. Jackson reported that gcc42 wouldn't build for him either, so maybe he had something else going on. I think I'll apply the patch anyway, if someone else doesn't get to it first.
Ryan, I've been out of the loop most of the week, but I've been looking at this as well and am encountering a problem getting Octave to build properly due to some issue with BLAS/veclib under Leopard. I'll report back more shortly. -Brent
participants (3)
-
Brent Fulgham
-
Joseph C. Slater PE, PhD
-
Ryan Schmidt