[Bug preprocessor/56306] New: -m32 does not support all includes

[Bug preprocessor/56306] New: -m32 does not support all includes

[uwe.seidler@siemens-enterprise.com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306

             Bug #: 56306
           Summary: -m32 does not support all includes
    Classification: Unclassified
           Product: gcc
           Version: 4.3.4
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: uwe.seidler@siemens-enterprise.com


Created attachment 29437
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29437
simple test program

Scenario: Compilation of a 32bit application on a 64bit host.
For "compiler internal" header files the preprocessor accesses the corret
header files, e.g. #include <bits/stdc++.h> includes 32/bits/stdc++.h.

For includes located somewher in the sysroot folders this usefull mechanism
does not work.

gcc-4.3 -m32 curlbr.c 
does not work if 32bit variant of curlbuild.h is provided in a 32/curl folder.

[Bug preprocessor/56306] -m32 does not support all includes

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|minor                       |enhancement

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-13 12:09:58 UTC ---
Well, there is no multilib setup for includes.  include files should work
for all multilibs.  In this case this is a bug of whoever provides curlbuild.h.

I don't see how this is a bug in GCC, so I'm re-labeling it as enhancement.

[Bug preprocessor/56306] -m32 does not support all includes

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-02-13 12:22:19 UTC ---
GCC can obviously alter its internal include paths to its own headers because
it knows what they contain and how to find the contents. It can't possibly know
about arbitrary non-GCC paths or whether it's correct or safe to append "32" to
those paths.

[Bug preprocessor/56306] -m32 does not support all includes

[uwe.seidler@siemens-enterprise.com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306

--- Comment #3 from Uwe Seidler <uwe.seidler@siemens-enterprise.com> 2013-02-13 12:35:34 UTC ---
enhacemant is ok

[Bug preprocessor/56306] -m32 does not support all includes

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Debian and Ubuntu solves this using the mutli-arch (which GCC has support for a
few years now).

But this is a distro issue rather than a GCC issue.