On 5/5/06, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
Dan Nicholson wrote:
Yes, we don't want the dependency. However, since we are doing a patch
anyway, why not just patch configure to remove the ed script and patch
libtool directly to the final result?
libtool is generated during configure, I think by ltmain.sh. I
suppose we could just do the sed after configure completes. I don't
think there'd be any harm in that.
I admit though that the sed is interesting, but most users won't even
look at it unless we put it directly into the book. Without looking it
up, I don't know what the
> +:a
> +$!{
> + N
> + ba
> +}
does. I know the :a is a label and I suspect the N is next and the ba
means jump back to the :a label, but it looks like it does nothing to me.
Well, it's not in there just for fun. ed, apparently, does things a
bit differently when it receives the q command. It quits where it is
and gives you the file back. sed, though, will q at the line your on
and drop all remaining lines. This is a problem since only the first
soname_spec needs to be matched. You can't just quit the sed script
after the first match because you lose the rest of the file.
Instead, it makes the :a label. Then says "If not the last line ($),
do this block {}." Inside the block, the next line is read (N), and
then branch (b) back to label a. Basically, it just makes the script
do nothing after the part I actually want done, like you say. Someone
that really knows sed could probably figure out a better way.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
