On Thu, 18 Mar 2004, Tor Arntsen wrote:

> curl/aclocal.m4 actually detects which compiler mode you're using, so that
> seems to be a good place to start. The code is all there (search for irix6),
> it's just to set a variable to lib, lib32 or lib64. Then that info has to be
> carried over to configure.ac, but I'm not sure how that's done. In that file
> the expression LDFLAGS="$LDFLAGS -L$EXTRA_SSL/lib" would have to be changed
> slightly, that final 'lib' would have to be a variable, carried over from
> aclocal.m4 I guess.

Well, they're all "merged" into the output configure script in the end.
aclocal.m4 is generated by aclocal, and then contains the m4-functions
configure.ac uses but doesn't provide by itself - kind of like an include file
to configure.ac. The acinclude.m4 is also like an included file, but hand-
written by us to provide useful functions for the configure.ac script.

I read that part of the generated script, and it seems it sets the variable
$libsuff to the "proper" suffix to use. To me, it seems we can then use
[blabla]/lib$libsuff in the configure.ac file to get the paths setup correctly
on the various IRIX "modes".

Try the attached patch and see if it is in the right direction!

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]