libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SCO/bugfix patch 7 of 10: Improve SCO platform support


From: Ralf Wildenhues
Subject: Re: SCO/bugfix patch 7 of 10: Improve SCO platform support
Date: Tue, 1 Nov 2005 07:02:06 +0100
User-agent: Mutt/1.5.9i

Hi Kean,

* Kean Johnston wrote on Mon, Oct 31, 2005 at 06:43:03PM CET:
> >Patch 7 of 10 attached ...
> 
> Here's a re-submission using install_libdir instead of the
> 'instrpath' hack I invented.

> Rationale:
> 
> I like it when things work on my platform :)

Ugh.  It's really difficult to judge over this huge patch -- would have
been much easier without the SCOABSPATH part.  Also, I haven't checked
closely yet (other eyes appreciated!), so I'll only give a few
suggestions:

- the SCOABSPATH stuff should likely be replaced by a generic libtool
option to achieve the same thing, or dropped.  Failing that, libtool
should to things on SCO the way it does on other platforms, ie. hardcode
the stuff that's not found by default.  (New features are post 2.0, by
the way.)

- You may and should use `~' as command separator in *_cmds, together
with newlines.  For example:
  foo_cmds='ls~echo~cat baz~
            if $foo; then bar; fi'

- Ideally, C++ support should be tested with CVS HEADs template library
tests first.. but that is optional.

- the `-belf' setting (sco3.2v5*) vanished completely:
| -  sco3.2v5*)
| -    _LT_AC_TAGVAR(lt_prog_cc_shlib, $1)='-belf'

Oversight?  If not: it's the only cruft that uses lt_prog_cc_shlib at
all, so the whole bag of that can go as well.

- the ChangeLog entry is, umm, a bit terse.  But granted, it's not
needed until the rest is in good shape.

By the way, is there good online documentation for these systems' ld and
dynamic loader?

Cheers,
Ralf

> 2005-10-24  Kean Johnston  <address@hidden>
> 
>       * libtool.m4: Complete overhaul of SCO support.
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]