Re: i386-none not in remapping table
David Raeker-Jordan wrote:
>I have an unstable system with a 2.2.19 kernel. I am trying to compile a
>2.4.17 kernel, but I get the following error when I run "make-kpkg clean"
>
>claire:/usr/src/linux-2.4.17/linux# make-kpkg clean
>dpkg: warning, architecture 386-none' not in remapping table
>rm -f modules/modversions.h modules/ksyms.ver debian/files stamp-build
>stamp-configure stamp-source stamp-image stamp-headers stamp-src stamp-diff
>stamp-doc stamp-buildpackage stamp-libc-kheaders stamp-debian
>test ! -f .config || cp -pf .config config.precious
>test -f Makefile && make ARCH=3Di386-none distclean
>make[1]: Entering directory /usr/src/linux-2.4.17/linux'
>Makefile:243: arch/i386-none/Makefile: No such file or directory
>make[1]: *** No rule to make target =01rch/i386-none/Makefile'. Stop.
>make[1]: Leaving directory /usr/src/linux-2.4.17/linux'
>make: [clean] Error 2 (ignored)
>test ! -f config.precious || mv -f config.precious .config
>rm -rf debian/tmp-source debian/tmp-headers debian/tmp-image
>test -f stamp-building || test -f debian/official || rm -rf debian
>
>
>If I run make-kpkg --arch i386 clean, I do not get any error messages, but
>running "make-kpkg kernel_image" yields these error messages at the end of
>the compile:
>
>make[1]: Entering directory /usr/src/linux-2.4.17/linux'
>Makefile:243: arch/i386-none/Makefile: No such file or directory
>make[1]: *** No rule to make target =01rch/i386-none/Makefile'. Stop.
>make[1]: Leaving directory /usr/src/linux-2.4.17/linux'
>make: *** [stamp-build] Error 2
>
>
>If I run "make-kpkg --arch i386 kernel_image", I get the following error
>messages at the end of the compile:
>
>make[1]: i386-linux-gcc: Command not found
>make[1]: *** [init/main.o] Error 127
>make[1]: Leaving directory /usr/src/linux-2.4.17/linux'
>make: *** [stamp-build] Error 2
>
>I have searched google and the debian mail archives, but the best answer I
>could find was to make sure all required packages were up to date. (They
>are) I think I recall reading about a problem with binutils, but the errors
>do not seem to be the same as what I am getting. I even found one posting
>with the same error, but it appears no one had an answer.
>
>Thanks in advance for any assistance.
I also encountered this problem when I used the backported dpkg and dpkg-
dev for Potato from Marillat's apt site. I don't know what causes this,
but I figured out some work-arounds for this. It's a problem with dpkg
1.9.x if I remember right...
Make the following symlinks. it should be enough for you to compile
a kernel, but you're not assured if that'll be enough to compile custom
debian packages:
i386-linux-ar -> /usr/bin/ar
i386-linux-as -> /usr/bin/as
i386-linux-cpp -> /usr/bin/cpp
i386-linux-gcc -> /usr/bin/gcc
i386-linux-ld -> /usr/bin/ld
i386-linux-nm -> /usr/bin/nm
i386-linux-objcopy -> /usr/bin/objcopy
There's ought to be a better way. I noticed that it prefixes i386-linux-
to the command. Where can I change the configs of dpkg or whatever causes
this so that i386-linux- would not be prefixed to the command? please help
on this!
Paolo Alexis Falcone
__________________________________
www.edsamail.com
Reply to: