This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: fatal error: gnu/stubs-32.h: No such file
- From: Andrew Haley <aph at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: David Starner <prosfilaes at gmail dot com>, gcc at gcc dot gnu dot org
- Date: Wed, 24 Jul 2013 10:18:43 +0100
- Subject: Re: fatal error: gnu/stubs-32.h: No such file
- References: <CAMZ=zj40GLLXB0toTGhpJihm--eMYMd643SOVGcPUg+LpRuZ8g at mail dot gmail dot com> <51EF8D98 dot 3060005 at redhat dot com> <51EF91C2 dot 5090002 at redhat dot com> <51EF92C1 dot 7020005 at redhat dot com> <51EF98B7 dot 3020105 at redhat dot com>
On 07/24/2013 10:04 AM, Florian Weimer wrote:
> On 07/24/2013 10:39 AM, Andrew Haley wrote:
>
>> Well, of course. It's a prerequisite for building GCC. I presume that
>> Debian has the same abilities as Fedora, where if you want to build GCC
>> you just type
>>
>> yum-builddep gcc
>>
>> and Fedora installs all the build reqs for GCC.
>
> Yes, "apt-get build-dep gcc" should work, but will install quite a bit
> of other stuff that's not needed for building the more popular front ends.
That is not of any significant consequence.
>>> I don't think that's easy to change because of the way dpkg handles file
>>> conflicts (even if the files are identical) and how true multi-arch
>>> support is implemented in Debian.
>>
>> But hold on: if I just wanted to compile C programs I'd use the system's
>> C compiler. Anyone building GCC for themself has a reason for doing so.
>
> I suspect a fairly common exercise is to check if the trunk still has
> the bug you're about to report.
Right, so it should be built the right way.
Andrew.