Debian Developers - request for diversion + please help to determine default targets

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > June 2004 > request for diversion + please help to determine default targets





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author request for diversion + please help to determine default targets
Nikita V. Youshchenko

2004-06-16, 5:55 pm

Hello.

I'm (de-facto) co-maintainer of dpkg-cross, the debian cross-compiling
support package.

One of the problems with debian package cross-compilation comes from
dh_strip, that just calls "strip" binary. It's ok for native compilation,
but for cross-compilation will cause problems unless binutils-multiarch is
installed.

A good way to deal with this is fixing dh_strip to use $STRIP environment
variable (if set) to locate strip binary. However, I was told [1] that
debhelper maintainers don't like this idea.

So I'm going to solve this issue by diverting dh_strip by a script, that
will:
- locate appropriate strip binary,
- if binary name is not "strip", create a temporary directory and a symlink
named "strip" there that will point to the strip binary,
- set PATH such that correct strip binary will be called
- execute original dh_strip
- remove temporary directory if one was created.

Debian policy requires to discuss any diversion in debian-devel.
It is OK to divert in this case?
Note that dpkg-cross already diverts dpkg-shlibdeps and dpkg-buildpackage.

One more question.
I'm going to detect strip binary that can deal with files for $(arch) by
checking /usr/bin/strip and several common locations for cross-strip, and
parsing the "supported targets" line of --help output of the found
binaries.

nikita@bliss:~> strip --help 2>&1 | grep 'supported targets'
strip: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32
elf32-little elf32-big elf64-x86-64 elf64-little elf64-big srec symbolsrec
tekhex binary ihex trad-core

nikita@bliss:~> arm-linux-strip --help 2>&1 | grep 'supported targets'
arm-linux-strip: supported targets: elf32-littlearm elf32-bigarm
elf32-little elf32-big srec symbolsrec tekhex binary ihex

To make this work on all archs, I need a table, what string to search in
supported targets for each debian architecture?
First targets listed by my deb installation of cross-binutils for several
linux targets are:
'elf32-i386' for x86-linux
'elf64-alpha' for alpha-linux
'elf32-littlearm' for arm-linux
'elf32-hppa' for hppa-linux
'elf64-ia64-little' for ia64-linux
'elf32-m68k' for m68k-linux
'elf32-tradbigmips' for mips-linux
'elf32-tradlittlemips' for mipsel-linux
'elf32-powerpc' for powerpc-linux
'elf32-s390' for s390-linux
'elf32-sparc' for sparc-linux
Is it ok to use those? What should be used for amd64 and hurd targets?

Nikita

[1] http://lists.debian.org/debian-embe...6/msg00067.html


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Martin Michlmayr

2004-06-16, 5:55 pm

* Nikita V. Youshchenko <yoush@cs.msu.su> [2004-06-16 01:44]:
> A good way to deal with this is fixing dh_strip to use $STRIP environment
> variable (if set) to locate strip binary. However, I was told [1] that
> debhelper maintainers don't like this idea.


You haven't said what's wrong with using binutils-multiarch.
--
Martin Michlmayr
tbm@cyrius.com


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Nikita V. Youshchenko

2004-06-16, 5:56 pm

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> * Nikita V. Youshchenko <yoush@cs.msu.su> [2004-06-16 01:44]:
>
> You haven't said what's wrong with using binutils-multiarch.


binutils-multiarch is huge, and technocally not required when binutils for=
=20
target are available. And (as binutila-multiarch description states)=20
binutils for target are needed anyway for cross-builds.

So when cross-compiling, we do always have a working strip for target. I=20
believe that making use of it is much better than install additional 18M=20
package.
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAz9BasTbPknTfAB4RAobyAJ0RuU1LBUWf
cGJVO5jIy3wSFhV6eQCgrIhy
AL+5ScpRDtwgBUJH6G+Y05Q=3D
=3DFMSo
=2D----END PGP SIGNATURE-----
Raphael Bossek

2004-06-16, 5:56 pm

Quoting Martin Michlmayr:
> Nikita V. Youshchenko <yoush@cs.msu.su> [2004-06-16 01:44]:
> environment
>
> You haven't said what's wrong with using binutils-multiarch.

binutils-multiarch is for all the folks who uses the default trunc of Debian
and its binutils and GCC. People who have to deal with embedded devices uses
3rd party binaries, like me for example. I have to deal with Hard Hat Linux
sometimes with Denk's ELDK (www.denx.de) binutils and GCC. I have to use
these tools because nobody can tell me which after-effects I will catch
mixing the environment with binutils-multiarch from Debian. I do not like to
find it out! I do not have the time and muse...

It's a question of freedom let me decide which tools I prefer for my work so
dh_strip should be a know-it-all implementation. It's so simple make
dh_strip gantler and prevent and diversion by dpkg-cross.

--
Raphael Bossek <bossekr@NOSPAMdebian.org>



--
+++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++
GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Guillem Jover

2004-06-16, 5:56 pm

Hi,

On Wed, Jun 16, 2004 at 01:44:21AM +0400, Nikita V. Youshchenko wrote:
> To make this work on all archs, I need a table, what string to search in
> supported targets for each debian architecture?


> Is it ok to use those? What should be used for amd64 and hurd targets?


elf32-i386 for i386-gnu (hurd-i386)
elf32-i386-freebsd for i386-kfreebsd-gnu (kfreebsd-i386)

regrads,
guillem


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2009 webservertalk.com