[Top][All Lists]

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

[bug-gnu-libiconv] Re: adding version identification to libiconv and lib

From: amores perros
Subject: [bug-gnu-libiconv] Re: adding version identification to libiconv and libintl
Date: Tue, 22 May 2007 01:58:11 +0000

Attaching result of diff -r -u3 --unidirectional-new-file

This version removes the use of BASH_REMATCH, and
changes the script opening to say /bin/sh.

I used a bunch of grep and cut to extract the numeric
version portions after all.

I also added a grep check that the rc template input
file actually appears to have an rc version section.

I did not revise the Makefile.am invocations to move the
linker invocations into the script, because I was hesitant,
because I'm not sure how to invoke the linker (or
compiler -- I'm not sure which programs exactly
are involved).

If that part gets moved into the script, won't the
caller need to pass any linker flags and the linker
invocation and anything relevant that may have
been customized, to the script, so it can call the
correct one?

I suppose $LD, and $WINDRES, and $LDFLAGS, and
I really don't know what all, could be passed, but
I don't know if that covers everything relevant?

Possibly include flags might be needed as well,
if there are includes in the RC file

I'm quite sure you've experienced with cross-compiling,
where it is important that the correct compiler
and linker be called.

In any case, perhaps you could check if the script now
looks portable enough.

Like the way Microsoft Office Outlook works? YouÂ’ll love Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507

reply via email to

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