Hello Neil,
could it be that my emdebian repositories are not set up correctly? Here is the content of sources.list:
# deb http://ftp.ch.debian.org/debian/ lenny main
deb http://ftp.ch.debian.org/debian/ lenny main
deb-src http://ftp.ch.debian.org/debian/ lenny main
deb http://security.debian.org/ lenny/updates main
deb-src http://security.debian.org/ lenny/updates main
deb http://buildd.emdebian.org/emdebian/ unstable main
deb http://www.emdebian.org/debian/ unstable main
# deb http://buildd.emdebian.org/emdebian/ unstable main
# deb-src http://buildd.emdebian.org/emdebian/ unstable main
# deb-src http://buildd.emdebian.org/emdebian/ testing main
And the things you asked for:
debian:~# cat /etc/dpkg-cross/cross-compile
#
# /etc/dpkg-cross/cross-compile: configuration for dpkg-cross
#
# default architecture for dpkg-cross (to avoid always typing the -a option
# if you do cross installations only for one architecture)
# Note: default_arch is managed by debconf - it can be overridden
# if ~/.dpkg-cross/cross-compile exists or by specifying an
# architecture on the command line.
# Use '[sudo] dpkg-reconfigure dpkg-cross' to change this value.
default_arch = arm
# All subsequent variables may be removed (and/or become
# unsupported) at any time.
#
# general section: paths of cross compiling environment
#
# you can set the following variables here:
# crossprefix: prefix for cross compiling binaries; default: $(DEB_HOST_GNU_SYSTEM)-
# crossbase : base prefix for the following; default: /usr
# crossdir : base directory for architecture; default:
# $(CROSSBASE)/$(DEB_HOST_GNU_TYPE)
# crossbin : dir for binaries; default: $(CROSSDIR)/bin
# crosslib : dir for libraries; default: $(CROSSDIR)/lib
# crossinc : dir for headers; default: $(CROSSDIR)/include
# maintainer : maintainer name to pass to original dpkg-buildpackage
# in -m option. If not set at all, don't pass a -m, thus
# dpkg-buildpackage will use the name from the changelog
# file. If set to the special string CURRENTUSER,
# dpkg-buildpackage will use the name from the
# changelog, too, but signing the .changes will be done
# as the current user (default key).
# removedeps : comma-separated list of package names that should be removed
# from depends/conflicts/etc fields
# keepdeps : comma-separated list of package names that should be kept
# in depends/conflicts/etc fields as is, without adding
# -arch-cross.
#
# In preparation for merging dpkg-cross into dpkg, the previous
# defaults have been removed.
debian:~# dpkg-architecture -aarm -qDEB_HOST_GNU_TYPE
bash: dpkg-architecture: command not found
debian:~# ls /etc/dpkg-cross/archtable.d/ -l
total 4
-rw-r--r-- 1 root root 793 2008-10-11 22:36 archtable.default
debian:~# perl -MDebian::DpkgCross -e 'print (check_arch("arm")."\n");'
debian:~# perl -MDebian::DpkgCross -e 'print (&get_architecture()."\n");'
debian:~# perl -MDebian::DpkgCross -e '&read_config; print (&get_architecture()."\n");'
arm
debian:~# ARCH=arm perl -MDebian::DpkgCross -e 'print (&get_architecture()."\n");'
arm
debian:~#
Thanks,
Marco
-----Original Message-----
From: Neil Williams [mailto:codehelp@debian.org]
Sent: Tue 2/3/2009 10:13 AM
To: Hoefle Marco
Cc: debian-embedded@lists.debian.org
Subject: Re: FW: migrating from uClinux to emdebian crush on a Xscale PXA270 board
On Tue, 3 Feb 2009 09:15:26 +0100
"Hoefle Marco" <Marco.Hoefle@nanotronic.ch> wrote:
> >> - I installed the arm cross compiling tools with:
> >> # apt-get install libc6-armel-cross libc6-dev-armel-cross
> >> binutils-arm-linux-gnueabi gcc-4.3-arm-linux-gnueabi
> >> g++-4.3-arm-linux-gnueabi
Why that way around? emsetup will do that for you once the other
problem is fixed.
> >> -tried to use emsetup:
> >> debian:~# emsetup
> >> Could not determine the default architecture, please use emsetup --arch
(To use emsetup without --arch, set a default cross-building
architecture in 'dpkg-reconfigure dpkg-cross' - you've currently got it
set to 'None'.)
> >> debian:~# emsetup --arch
> >> Could not determine the default architecture, please use emsetup --arch
> >> debian:~# emsetup --arch arm
>
> >> Error: dpkg-cross does not currently support "arm"
> >> debian:~# man emsetup
>
> >Try to set up the architecture running:
> ># dpkg-reconfigure dpkg-cross
>
> I did this but i get the same error when using emsetup:
> debian:~# dpkg-reconfigure dpkg-cross
What did you select at this point?
Note that in a chroot, you may have left the debconf priority too high
to see the question. Check your debconf priority.
> debian:~# emsetup
>
> Error: dpkg-cross does not currently support "arm"
> debian:~#
Something is badly wrong with your environment / setup.
I need all relevant information on the setup of this box - please
report a bug against dpkg-cross and include the content of:
/etc/dpkg-cross/cross-compile
The output from these test commands:
$ dpkg-architecture -aarm -qDEB_HOST_GNU_TYPE
$ ls /etc/dpkg-cross/archtable.d/ -l
$ perl -MDebian::DpkgCross -e 'print (check_arch("arm")."\n");'
$ perl -MDebian::DpkgCross -e 'print (&get_architecture()."\n");'
$ perl -MDebian::DpkgCross -e '&read_config; print (&get_architecture()."\n");'
$ ARCH=arm perl -MDebian::DpkgCross -e 'print (&get_architecture()."\n");'
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/