Re: "checking for cholmod_start in -lcholmod... no"

[Electronnix]

Mike Miller wrote
> That's good stuff, that might help further diagnose this, but what I
> need to see first as I said before is the config.log file that Octave's
> configure script produces. I don't see that at any of your links.

My apologies, I really wasn't aware config.log was an actual file generated
in the process :(.
(I thought you meant the text generated in the console by the configure
script)
So here is the link for it:
http://www.cobrasov.com/CoBra%20Project/config.log


Mike Miller wrote
> I'm not sure if this will fix anything, but I notice you have
> 
>   --with-amd-includedir=usr/include/suitesparse
> 
> and so on for the SuiteSparse libraries. Notice "usr" instead of "/usr".

Boy, that's a good catch. You have a sharp eye.
All the   "--with-xxxxx-includedir="    options were missing the leading /

I fixed them all, but you were right, that did not fix the issue.
Looks like the configure script searches /usr/include/suitesparse by default
when it looks for headers, so these options are actually redundant
I only used them because I read other threads that mentioned them.

----------
Electronnix




--
View this message in context: 
http://octave.1599824.n4.nabble.com/checking-for-cholmod-start-in-lcholmod-no-tp4663980p4664117.html
Sent from the Octave - General mailing list archive at Nabble.com.