Public SourceMage Discussion List

[Javier Vasquez <j.e.vasquez.v AT gmail.com>]

> BTW, I missed the point of your 2nd argument on the non convenient
> aspects of "--as-needed":
>
> +++++++
> 2) it breaks some spells. Some spells are fixable, but some may not
> be. The most common problem is a spell directly using a dependency,
> but not linking to it directly, which can in certain cases lead to a
> problem.
> +++++++
>
> Sorry, I got biased by it being the best course of action...
>
> Any ways I'll take a look at the UP_TRIGGERS, and then run a script to
> get all spells depending upon libpng according to "ldd".  Between
> those 2 things, maybe the trials gets easier, :-)


BTW, I went through the effort of updating libpng.  Not a pleasant
experience, :-(  It took me more then a pretty involved weekend, :-)

I believe "--as-needed" is not only a good recommendation, perhaps it
should be the default for the unaware, and then when becoming aware of
things the user can change that if required.

There were spells that didn't link just because before they were
marked to need the old lib.  Those require a plain dispel, and then a
new cast.

Recompilation was not the only thing needed.  Several spells required
update and/or changes (the interface offered by 1.5/1.6 is different
than the one offered on 1.2).  See some of the bugs I files due to
that:

http://www.sourcemage.org/issues/623
http://www.sourcemage.org/issues/622
http://www.sourcemage.org/issues/620
http://www.sourcemage.org/issues/617
http://www.sourcemage.org/issues/616
http://www.sourcemage.org/issues/615
http://www.sourcemage.org/issues/614
http://www.sourcemage.org/issues/606

The inner dependencies between the different spells made several
recompilations required, which is a pretty manual process...

Any ways, I would say, to reduce the manual interaction the most
possible, then "-as-needed" is required.

On a similar topic, but something I would add in a different thread
when having time to comment on it, happens to libgmp, libmpfr and
libmpc.  Fortunately sorcery creates some artificial library links
(not sure why, looks like a bug, that becomes a feature), and that
solves the problem.  However, for one of the spells (don't remember
which), the links are created from /usr/...  which on a 2nd
compilation are lost and that breaks things.  Problem is that
UP_TRIGGERS do not help at all, since evertything breaks, including
sorcery, once the links are lost.  Therefore a manual assist is
required.  My work around is that any time I re-compile those spells,
I break the /usr/... artificial links, and create ones to the same
directories, which allow next re-compilation not to break the links...

Once I have some time to look at those spells (I've updated them given
I'm using 4.8.2 gcc), I'll cover that in a different spell.

Thanks,

-- 
Javier.