Kevin Ryde <[EMAIL PROTECTED]> writes:
> What would be an example of a system with the "int" RETSIGTYPE that
> the macro tests for?
I don't know of any such systems that are still in practical use. As
far as I know, that macro is no longer needed, though we should keep
it around for backward-com
On Mon, Oct 20, 2003 at 08:42:06PM +0100, Richard Dawe wrote:
> The pattern rules (e.g.: "%.o: %.c") don't seem to be in the Single Unix
> Specification and therefore may not be very portable across Unices.
Dunno about the SUS, but they're certainly not portable. AFAIK,
they're specific to GNU ma
Hello.
[EMAIL PROTECTED] wrote:
>
> Solaris 2.6, Autoconf 2.57.
>
> I guess I need to replace my use of $< in a Makefile.
>
> In a Makefile.in I have:
>
> %.1: ../pod/%.pod
> pod2man --center="SWISH-E Documentation" --lax --release='$(VERSION)' $< > $@
>
> When I build on Solaris $< d
Solaris 2.6, Autoconf 2.57.
I guess I need to replace my use of $< in a Makefile.
In a Makefile.in I have:
%.1: ../pod/%.pod
pod2man --center="SWISH-E Documentation" --lax --release='$(VERSION)' $< > $@
When I build on Solaris $< doesn't seem to get used:
pod2man --center="SWISH-E Docu
Hi all,
does anyone know about strange runtime errors
when calling static member functions within an
executable that is linked with shared/static libtool libraries ?
The error occurs during the initializing procedure.
Kai
--
http://echempp.sourceforge.net
Kai Ludwig
Universität Tübingen
Inst
Bob Lockie <[EMAIL PROTECTED]> writes:
> :snippit of my configure.in:
>
> dnl id3lib library (required)
> AC_CHECK_LIB( [z], [deflate],
>configure_enable_id3lib="yes",
>configure_enable_id3lib="no", )
You are overriding the