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

Re: Automated CPU-optimised-/cross-building of Debian-packages.



On Sat, 9 Dec 2000, Colin Watson wrote:

> Leen Besselink <leen@wirehub.nl> wrote:
> >Does anyone know how to do cross and/or CPU-optimised building of Debian
> >packages, preferable with the Debian 'standardtools' ?
>
> For cross-compiling, try the dpkg-cross package.

Yes I just found that one out myself, pretty dim of me. :)

>
> For optimized compiling, try the pentium-builder package (the name
> notwithstanding, I don't think it's just for the i386 architecture).

I also found that package, but for some reason, I think dpkg-buildpackage
overwrites my environment settings ??

>
> >Normally when I build a debian package I do this:
> >
> >dpkg-source -x package-name-version.dsc
> >cd package-name-version
> >dpkg-buildpackage
>
> 'dpkg-buildpackage -rfakeroot' is good, if you install the fakeroot
> package, since then you don't need to be root to build packages.

well, as a test I did this:
apt-get install gcc-m68k-linux
(which also wanted to install the appropriate binutils)

so now when I do this:
dpkg-buildpackage -rfakeroot -am68k

I get:
dpkg-buildpackage: source package is tar
dpkg-buildpackage: source version is 1.13.17-2
dpkg-buildpackage: source maintainer is Bdale Garbee <bdale@gag.com>
dpkg-architecture: warning: Specified GNU system type m68k-linux does not
match gcc system type i386-linux.
 fakeroot debian/rules clean DEB_BUILD_ARCH=i386 DEB_BUILD_GNU_CPU=i386
DEB_BUILD_GNU_SYSTEM=linux DEB_BUILD_GNU_TYPE=i386-linux
DEB_HOST_ARCH=m68k DEB_HOST_GNU_CPU=m68k DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=m68k-linux

[.. so after a while I get ..]

checking whether the C compiler (m68k-linux-gcc -O2 -g -Wall ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.
make: *** [build-stamp] Error 1
make: Leaving directory `/usr/src/leen/tar-1.13.17'

Looking at the config.log file it says:

configure:938: checking whether the C compiler (m68k-linux-gcc -O2 -g
-Wall ) works
configure:954: m68k-linux-gcc -o conftest -O2 -g -Wall   conftest.c  1>&5
configure:951: warning: return-type defaults to `int'
/usr/m68k-linux/bin/ld: cannot open crt1.o: No such file or directory
configure: failed program was:

#line 949 "configure"
#include "confdefs.h"

main(){return(0);}

When I look up what package(s) contains crt1.o they are these (on the
website):

usr/i486-linuxlibc1/lib/crt1.o                    oldlibs/libc5-altdev
usr/i486-linuxlibc1/lib/gcrt1.o                   oldlibs/libc5-altdev
usr/lib/Mcrt1.o                                   devel/libc6-dev
usr/lib/checker/i686-pc-linux-gnu/chkr-crt1.o     devel/gccchecker
usr/lib/crt1.o                                    devel/libc6-dev
usr/lib/gcc-lib/i386-gnu/2.95.2/crt1.o            devel/gcc-i386-gnu
usr/lib/gcrt1.o                                   devel/libc6-dev
usr/lib/oskit/unix/crt1.o                         devel/oskit

When I install the oskit (what else can it be ? turns out not to be it)
and an updatedb later (and un umount of a vfat-partition ;)

I find these:
/usr/lib/crt1.o
/usr/lib/gcrt1.o
/usr/lib/Mcrt1.o
/usr/lib/oskit/unix/crt1.o

I'm now have no idea left what this can be. Any ideas, would really help.
:)



Reply to: