On Fri, Jul 23, 2010 at 05:48:09PM +0100, Dr. David Kirkby wrote:
> On 07/23/10 03:52 PM, Carl Witty wrote:
>> the>/dev/null 2>&1 means we don't get to see the actual compile error.
>>
>> It would be interesting, and perhaps informative, to see what the error was.
>>
> That's one of the "features" of libtool. Does anyone know how to stop it
> sending the output to /dev/null?
libtool has a '-no-suppress' option for that.
_Hopefully_ editing src/src/Makefile.in and changing
LTCOMPILE = $(LIBTOOL) --tag=CC --mode=compile $(CC) $(DEFS) \
$(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \
$(AM_CFLAGS) $(CFLAGS)
to
LTCOMPILE = $(LIBTOOL) --tag=CC --mode=compile $(CC) -no-suppress $(DEFS) \
$(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) \
$(AM_CFLAGS) $(CFLAGS)
will do the trick. (If Makefile.in isn't regenerated from Makefile.am
accidentally.)
-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
