On Mon, Oct 28, 2013 at 2:30 AM, Irek Szczesniak <[email protected]> wrote:
> On Mon, Oct 28, 2013 at 12:55 AM, ольга крыжановская
> <[email protected]> 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.
>>
>> Do you know where the string 'x86_64-linux-gnu' comes from? Who
>> declares it? Is it created? What values do other platforms use?
>>
>> The only reference I could find is this one:
>> $ grep -r x86_64-linux-gnu /usr/include/
>> /usr/include/llvm-3.2/llvm/Config/config.h:#define C_INCLUDE_DIRS
>> "/usr/include/x86_64-linux-gnu:/usr/include/x86_64-linux-gnu:/usr/include"
>> /usr/include/llvm-3.2/llvm/Config/config.h:#define LTDL_SYSSEARCHPATH
>> "/lib:/usr/lib:/usr/local/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu"
>
> Well, this is a bug in debian. ast-ksh uses plain /usr/bin/cc and
> Roland Mainz's buildksh93.sh uses either gcc -std=gnu99
> -D_XOPEN_SOURCE=600 -D__EXTENSIONS__=1 or clang -std=gnu99
> -D_XOPEN_SOURCE=600 -D__EXTENSIONS__=1, which per POSIX should give a
> working compilation environment. Debian, and not ast-ksh, breaks this.
>
> Giovanni, if you would kindly file a bug against Debian's system
> includes which clearly states that specifying gcc -std=gnu99
> -D_XOPEN_SOURCE=600 -D__EXTENSIONS__=1 or clang -std=gnu99
> -D_XOPEN_SOURCE=600 -D__EXTENSIONS__=1 does not result in a working
> compilation environment where the X/OPEN and GNU extensions are
> available.
>
> This ball is now clearly in Debian's court. And it stinks like rotten flesh.

... or I should slap myself. On a coworkers machine the installation
of the 'libc6-dev-i386' package fixed the problem.

Now the question for Oliver and Olga is to figure out what cross
platform superclass package 'libc6-dev-i386' translates to so make
that a build dependency on all platforms.

Irek

Email secured by Check Point
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to