On Thu, Mar 11, 2010 at 06:51:57PM +0000, Dr. David Kirkby wrote:
> It looks like the code above might be linking the readline library (note
> the -lreadline) to produce a readline library (note the -o readline.so).
> That would seem an odd thing to do.
>
> Does the above command look a bit suspicious to you?
Python has a readline.so in its tree; it's probably linking that:
[...@aldur ~]$ locate readline.so | grep sage
/data/sage/sage-4.3/local/lib/python2.6/lib-dynload/readline.so
[...]
> Willem Jan Palenstijn wrote:
> > Are you using a parallel build? If so, there might be an error further up.
>
> Generally no. I have occasonally run parallel builds, but have tended to
> avoid them, as I don't trust them.
>
> The python build occasionally stalls at the point shown above, but with no
> error message at all.
If it's not a parallel build, there's still a -k flag ('keep going') to (GNU)
make that would cause make to keep building stuff until the failed command
actually blocks all remaining unbuilt targets, in which case the error might
still be hidden potentially far up in the log. Maybe some of the packages use
this flag internally? Maybe some non-GNU make behaves this way by default?
If it happens again, could you put the last thousand lines or so from the build
online somewhere? (Or even the entire log.) Maybe someone will notice something
strange.
-Willem Jan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
