Hi Olga,

On 28/10/13 00:55, ольга крыжановская wrote:
> Giovanni, I can reproduce your problem, with gcc 4.8 and clang as the
> compilers. As more than one compiler is affected, I think this is a
> problem in the system includes, in Debian specifically, as no other
> Linux has this trouble.

Note that I can reproduce the same issue on ubuntu 12.04 .

Debian has adopted their own implementation of multiarch. If I
understand well, Debian Multiarch allows to install libraries and header
files of whatever architecture you want on a given system. For instance
you can install arm 32 bits and mips 64 bits lib files and header files
on you running system which is based on x86 32 bits. This will allow,
for instance, to cross-compile or to run binaries of another
architecture via an emulator. The files will always be installed in the
same location, for instance, x86 64bit specific header files for a
system running a freebsd kernel will always be installed under
/usr/{lib,include}/x86_64-kfreebsd-gnu whereas the files for arm 32 bit
for a linux kernel will be in /usr/{lib,include}/arm-linux-gnueabi. It
is hard for me to better explain multiarch. If I can suggest some
selected-and-fast-to-read reading about Debian multiarch:

o "About" section of https://wiki.debian.org/Multiarch
o "Introduction" section, then  "Proposed general solution" section of
https://wiki.debian.org/Multiarch/TheCaseForMultiarch
o List of gnu triplet (x86_64-kfreebsd-gnu, arm-linux-gnueabi are called
gnu triplet) https://wiki.debian.org/Multiarch/Tuples


> Do you know where the string 'x86_64-linux-gnu' comes from? Who
> declares it? Is it created? What values do other platforms use?

If I run gcc -v on my x86_64 sytem, I can see in the output:
Target: x86_64-linux-gnu

And on a ARM virtual machine, I have:
Target: arm-linux-gnueabihf

See the link above to the list of gnu triplet for other values.

I am going to give other details about my issue in response to the mail
of Irek.


-- 
Giovanni Rapagnani
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to