Thinking about ltrace-0.5.3

Thinking about ltrace-0.5.3

[Joachim Nilsson]

Hi Yann!

I've been looking into integrating the latest ltrace, 0.5.3, with 
crosstool-NG.  It seems the maintainer has purged GNU Autotools from the 
tree and is now using a home baked configure et al.

This _could_ mean a fundamental change to 
scripts/build/debug/400-ltrace.sh, since --host and --build no longer 
apply, or some clever special handling, similar to "if [ version -gt 
0.5.3 ]", unless you decide to drop support for all prior ltrace versions?

How would you like to proceed?  Maybe you have some similar 
version-exception handling for other packages that you can recommend me 
looking at.

The "heavy lifting" of adapting 0.5.3 to cross-building seems to be done 
already by the openembedded guys, so it's more of a integration with 
crosstool-NG issue.

     
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/ltrace/files

Regards
  /Joachim


--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Thinking about ltrace-0.5.3

[Yann E. MORIN]

Joachim, All,

On Friday 01 January 2010 19:24:34 Joachim Nilsson wrote:
> I've been looking into integrating the latest ltrace, 0.5.3, with 
> crosstool-NG.  It seems the maintainer has purged GNU Autotools from the 
> tree and is now using a home baked configure et al.

Which I won't blame him for! I always found the autotools stuff hard to
work with, that's why crosstool-NG uses its own home-bread ./configure
as well...

> This _could_ mean a fundamental change to 
> scripts/build/debug/400-ltrace.sh, since --host and --build no longer 
> apply, or some clever special handling, similar to "if [ version -gt 
> 0.5.3 ]", unless you decide to drop support for all prior ltrace versions?

I do not want to drop older versions, until at least the next major relase
due late January.

> How would you like to proceed?  Maybe you have some similar 
> version-exception handling for other packages that you can recommend me 
> looking at.

I think something like (in pseudo-code):

config_opts=( "--prefix=..." "whatever" "common" "opts..." )
make_opts=( "whatever" "common" "opts..." )
if [ version < 0.5.3 ]; then
    config_opts+=( "--build=..." "--host=..." )
    make_opts+=( "whatever" )
else
    config_opts+=( "whatever" )
    make_opts+=( "whatever" )
fi
.../configure "${config_opts[@]}"
make "${make_opts[@]}"

Note: CT-NG relies (and checks for) a bash that understands arrays, so we
can safely use that, as it is easy to add multiple strings with spaces in
them.

> The "heavy lifting" of adapting 0.5.3 to cross-building seems to be done 
> already by the openembedded guys, so it's more of a integration with 
> crosstool-NG issue.

Very nice! Please, also check that any existing patch for previous versions
are still needed.

Waiting for your submission, then! (if you could submit Mercurial patches,
that would make my life easier to apply those patches).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'



--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Thinking about ltrace-0.5.3

[Joachim Nilsson]

On 01/01/2010 07:44 PM, Yann E. MORIN wrote:
> On Friday 01 January 2010 19:24:34 Joachim Nilsson wrote:
>    
>> This _could_ mean a fundamental change to
>> scripts/build/debug/400-ltrace.sh, since --host and --build no longer
>> apply, or some clever special handling, similar to "if [ version -gt
>> 0.5.3 ]", unless you decide to drop support for all prior ltrace versions?
>>      
> I do not want to drop older versions, until at least the next major relase
> due late January.
>    

OK!

>> How would you like to proceed?  Maybe you have some similar
>> version-exception handling for other packages that you can recommend me
>> looking at.
>>      
> I think something like (in pseudo-code):
> config_opts=( "--prefix=..." "whatever" "common" "opts..." )
> make_opts=( "whatever" "common" "opts..." )
> if [ version<  0.5.3 ]; then
>      config_opts+=( "--build=..." "--host=..." )
>      make_opts+=( "whatever" )
> else
>      config_opts+=( "whatever" )
>      make_opts+=( "whatever" )
> fi
> .../configure "${config_opts[@]}"
> make "${make_opts[@]}"
>    

OK, got it!

>> The "heavy lifting" of adapting 0.5.3 to cross-building seems to be done
>> already by the openembedded guys, so it's more of a integration with
>> crosstool-NG issue.
>>      
> Very nice! Please, also check that any existing patch for previous versions
> are still needed.
>    

Will do.

> Waiting for your submission, then! (if you could submit Mercurial patches,
> that would make my life easier to apply those patches).
>    

OK, I'll look into it.  I see you've documented the process well in 
docs/overview.txt, so I'll go with that.

Regards
  /Joachim

P.S.    Thanks for the bash completion stuff, I was really missing that 
from regular Makefiles. :-)


--
For unsubscribe information see http://sourceware.org/lists.html#faq