> I'm noticing similar problems for current CVS on Solaris 2.6.
one step back, this was a too early shot.
The problem was solaris' make, gmake works fine.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Münsterstr. 248
40470 Düsseld
> The Makefile created should not run "ar rc" but "libtool -static -o" instead
> Furthermore the following had to be replaced (safe for all platforms
> I presume):
>
> replace
>
> wmlscriptobjs = $(wmlscriptsrcs:.c=.o) $(wmlscriptsrcs:.y=.o)
>
>with
>
> wmlscriptobjs = $(wildcard
Andreas Fink schrieb:
>
> > > The Makefile created should not run "ar rc" but "libtool -static
> >-o" instead
> >
> >so you have to garantee libtool is available, which is not tested
> >while configure :(
>
> MacOS X has it available. Thats for sure. ar didnt work because some
> objects are mul
> The Makefile created should not run "ar rc" but "libtool -static -o" instead
so you have to garantee libtool is available, which is not tested
while configure :(
What's the problem wit "ar rc"?
> Furthermore the following had to be replaced (safe for all platforms
> I presume):
>
> replace
> > Ok would you mind adding the MacOS X issues I've posted as well? I'm
>> not a frequent configure.in hacker that I can be sure that it works
>> correctly.
>
>Can you please state which post you mean?
the one on Date: Fri, 2 Nov 2001 11:49:23 +0100
Changes in the config needed:
The Makefil
> Ok would you mind adding the MacOS X issues I've posted as well? I'm
> not a frequent configure.in hacker that I can be sure that it works
> correctly.
Can you please state which post you mean?
> Hmm. be aware that the binaries names will change due to that
> (example: /usr/local/sbin/bearerbo
Hi all,
this is a request for comments before I commit changes to CVS
regarding how the openssl libaries are detected within the configure
process:
This change should solve the problem that on different platforms the
openssl libs are not detected and hence no SSL support is compiled in
to the ga
