Re: ltconfig generation change for SCO builds

[Bob Friesenhahn]

The next release of libtool does not use 'ltconfig'.  You might want
to check libtool out of CVS and see what changes need to be made (if
any).

Bob

On Thu, 14 Nov 2002, Jonathan Schilling wrote:

> To the libtool maintainers,
>
> A change needs to be made to the generation of ltconfig in order for
> it to build correctly on SCO OpenServer when using the SCO UDK development
> kit (which is a different [more advanced] development kit than the "regular"
> one that comes with OpenServer).
>
> The change is to only set special_shlib_compile_flags if the regular
> compiler is being used (which needs the flags), and not set it if
> the UDK compiler is being used.  The diff as generated in ltconfig
> (with some nulled out debugging code) is:
>
> --- ltconfig..orig      Sun May 28 07:08:13 2000
> +++ ltconfig    Wed Oct  9 14:42:00 2002
> @@ -727,7 +727,12 @@
>    sco3.2v5*)
>      pic_flag='-Kpic'
>      link_static_flag='-dn'
> -    special_shlib_compile_flags='-belf'
> +    if `$compiler -V 2>&1 | egrep 'UX:cc' > /dev/null`; then
> +       echo "this is really UDK compiler" > /dev/null
> +    else
> +       echo "this is not the UDK compiler" > /dev/null
> +       special_shlib_compile_flags='-belf'
> +    fi
>      ;;
>
>    solaris*)
>
> Thank you very much.
>
> Jonathan Schilling    SCO/Caldera     address@hidden
>
>
> _______________________________________________
> Libtool mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool
>

======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen