On 5/22/12 12:48 PM, notMyUsername wrote: > > Alexander Hansen-2 wrote >> >> On 5/21/12 4:28 PM, notMyUsername wrote: >>> So since none of these variables are set outside of Homebrew I presume >>> that >>> what I need to do is get Homebrew to use different CXX and CSSFLAGS when >>> it >>> builds Octave in the first place? Is that where Octave is getting those >>> from? >> >> Yes. Octave encodes the compilers and flags that you use to build it. >> >> You can edit mkoctfile-3.6.1 and change the settings in that. >> You can also edit oct-conf.h and do the same thing > > Much thanks. I tried that and was able to build miscellaneous. However, so > far I have not been able to build optim (these are all dependencies of the > packages I actually need). optim won't link (regardless of compiler): > > Undefined symbols for architecture x86_64: > "_sdisna_", referenced from: > F__disna_optim__(octave_value_list const&, int) in > __disna_optim__.o > "_ddisna_", referenced from: > F__disna_optim__(octave_value_list const&, int) in > __disna_optim__.o > ld: symbol(s) not found for architecture x86_64 > > I'm about to give up. >
I'll redirect this thread, as this is a problem specific to the released version of the optim package when using Octave 3.6.0+ . The symbols which aren't being found are from LAPACK. -- Alexander Hansen, Ph.D. Fink User Liaison http://finkakh.wordpress.com/2012/02/21/got-job/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
