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

Problem during compile because of unknown gcc sytem type



Hello,

I'm trying build some debian packages from source, using a gcc which is
patched with the IBM Stack Protector. Unfortunately every time I
try build the packages, I get the following error message:

dpkg-architecture: warning: Unknown gcc system type i686-pc-linux-gnu,
 falling back to default (native compilation) 
 dpkg-architecture: warning: Specified GNU system type i386-linux does
 not match gcc system type i686-pc-linux-gnu, 

although I started with dpkg-buildpackage -ai386. Even using
dpkg-buildpackage -d -ai386 doesn't fix the problem.

Calling up dpkg-architecture with parameter shows the following output:

vollbracht@desktop:~$ dpkg-architecture
dpkg-architecture: warning: Unknown gcc system type i686-pc-linux-gnu,
falling back to default (native compilation) dpkg-architecture: warning:
Specified GNU system type i386-linux does not match gcc system type
i686-pc-linux-gnu. DEB_BUILD_ARCH=i386
DEB_BUILD_GNU_CPU=i386
DEB_BUILD_GNU_SYSTEM=linux
DEB_BUILD_GNU_TYPE=i386-linux
DEB_HOST_ARCH=i386
DEB_HOST_GNU_CPU=i386
DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=i386-linux

To solve the problem I edited dpkg-architecture and changed the
$gcc-variable to the correct path. 
This worked for the dpkg-architecture, but during compiling a tool i
got the following error-message:
dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table

This leads me to two questions:
1. Which other programmes/routines perform a CPU detecting during the
packaging process and how can I change it? 
2. Why doesn't the parameter -ai386 force build-package to generate i386
packages?
3. If dpkg claims to fall back to default, does this mean the
programm will run on a i386 cpu without problems?

In case of any questions, don't hesitate to mail me.

Thanks in advance

Greatings Uwe

===================================
Uwe Vollbracht
Student of Computer Science,  RWTH Aachen

e-mail:	uwe.vollbracht@post.rwth-aachen.de
===================================



Reply to: