for some reason I don't got your reply but I read it throught the web
interface.
I think the real error is
In file included from /usr/include/bits/errno.h:25:0,
                 from /usr/include/errno.h:36,
                 from ../../../zlib/zutil.h:38,
                 from ../../../zlib/crc32.c:29:
/usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or
directory
compilation terminated.
make[5]: *** [libz_a-crc32.o] Error 1
make[5]: Leaving directory
`/home/maartenvd1994/gdc_building/gdc/dev/gcc4.6.1/objdir/64/zlib'
make[4]: *** [multi-do] Error 1
make[4]: Leaving directory
`/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'
make[3]: *** [all-multi] Error 2
make[3]: Leaving directory
`/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'
make[2]: *** [all-stage1-zlib] Error 2
make[2]: *** Waiting for unfinished jobs....

I'll recompile and save the output to a file and post it here.

Looks like you can't even compile zlib.
You might try downloading zlib and compiling it to check whether that works at all.

maarten van damme Wrote:

> for some reason I don't got your reply but I read it throught the web
> interface.
> I think the real error is
> In file included from /usr/include/bits/errno.h:25:0,
>                  from /usr/include/errno.h:36,
>                  from ../../../zlib/zutil.h:38,
>                  from ../../../zlib/crc32.c:29:
> /usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or
> directory
> compilation terminated.
> make[5]: *** [libz_a-crc32.o] Error 1
> make[5]: Leaving directory
> `/home/maartenvd1994/gdc_building/gdc/dev/gcc4.6.1/objdir/64/zlib'
> make[4]: *** [multi-do] Error 1
> make[4]: Leaving directory
> `/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'
> make[3]: *** [all-multi] Error 2
> make[3]: Leaving directory
> `/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'
> make[2]: *** [all-stage1-zlib] Error 2
> make[2]: *** Waiting for unfinished jobs....
> 
> I'll recompile and save the output to a file and post it here.
> 
> for some reason I don't got your reply but I read it throught the web interface.<br>I think the real error is<br>In file included from /usr/include/bits/errno.h:25:0,<br>                 from /usr/include/errno.h:36,<br>
>                  from ../../../zlib/zutil.h:38,<br>                 from ../../../zlib/crc32.c:29:<br>/usr/include/linux/errno.h:4:23: fatal error: asm/errno.h: No such file or directory<br>compilation terminated.<br>make[5]: *** [libz_a-crc32.o] Error 1<br>
> make[5]: Leaving directory `/home/maartenvd1994/gdc_building/gdc/dev/gcc4.6.1/objdir/64/zlib'<br>make[4]: *** [multi-do] Error 1<br>make[4]: Leaving directory `/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'<br>
> make[3]: *** [all-multi] Error 2<br>make[3]: Leaving directory `/home/maartenvd1994/gdc_building/gdc/dev/gcc-4.6.1/objdir/zlib'<br>make[2]: *** [all-stage1-zlib] Error 2<br>make[2]: *** Waiting for unfinished jobs....<br>
> <br>I'll recompile and save the output to a file and post it here.<br><br><br>
> 

I had similar problems on debian testing x86_64. Apparently some files have been
moved and this causes those problems. For example, /usr/include/asm/errno.h is
now at /usr/include/x86_64-linux-gnu/asm/errno.h. Plain gcc failed to compile too.
I tried messing around with symlinks and environment variables but failed.
Then I have just compiled gdc on debian stable with --prefix=/opt/gdc/ (to not
mess up my system), installed it and moved files to debian testing. Before using
it I run

export PATH=/opt/gdc/bin/:$PATH
export LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/

and it works.

> I had similar problems on debian testing x86_64. Apparently some files have been moved and this causes those problems. For example, /usr/include/asm/errno.h is
> now at /usr/include/x86_64-linux-gnu/asm/errno.h. Plain gcc failed to compile too.
> I tried messing around with symlinks and environment variables but failed.

On Ubuntu the symlink exists.

/usr/include/asm -> /usr/include/x86_64-linux-gnu/asm/

I've created those symlinks and now libgomp is failing :s
I hope gdc (for D2) gets included in gcc so I can simply download it from
synaptic :D

2011/9/23 Trass3r <un@known.com>

> I had similar problems on debian testing x86_64. Apparently some files have
>> been moved and this causes those problems. For example,
>> /usr/include/asm/errno.h is
>> now at /usr/include/x86_64-linux-gnu/**asm/errno.h. Plain gcc failed to
>> compile too.
>> I tried messing around with symlinks and environment variables but failed.
>>
>
> On Ubuntu the symlink exists.
>
> /usr/include/asm -> /usr/include/x86_64-linux-gnu/**asm/
>

== Quote from maarten van damme (maartenvd1994@gmail.com)'s article
> I hope gdc (for D2) gets included in gcc so I can simply download it from
> synaptic :D

I don't think this will ever be a good solution.  The glacial and centralized nature of Linux packaging conflicts with the fast-moving nature of D.  For example, when I write D code I don't make even the slightest effort to support any compiler/phobos/druntime version other than the latest.  Most of my code would probably not even compile with a release from 6 months ago.

2011/9/23 dsimcha <dsimcha@yahoo.com>

> I don't think this will ever be a good solution.  The glacial and
> centralized
> nature of Linux packaging conflicts with the fast-moving nature of D.  For
> example, when I write D code I don't make even the slightest effort to
> support any
> compiler/phobos/druntime version other than the latest.  Most of my code
> would
> probably not even compile with a release from 6 months ago.
>
Debian unstable keeps up with the newest of the newest. There was even a
little update today.
And if you make another libphobos/libdruntime package then we can compile
that one ourselves if we need a newer phobos lib.

It's just so sad compiling it myself is so terribly failing. I wish someone could explain me how to do that in debian testing.

dsimcha wrote:

> == Quote from maarten van damme (maartenvd1994@gmail.com)'s article
>> I hope gdc (for D2) gets included in gcc so I can simply download it from
>> synaptic :D
> 
> I don't think this will ever be a good solution.  The glacial and
> centralized
> nature of Linux packaging conflicts with the fast-moving nature of D.  For
> example, when I write D code I don't make even the slightest effort to
> support any
> compiler/phobos/druntime version other than the latest.  Most of my code
> would probably not even compile with a release from 6 months ago.
Once you have a package it's easy enough to `apt-get source`/download srpm, replace the code and rebuild producing new packages. rpm/apt-get makes sure you got all the dependencies and someone else has already tuned all the paths and any quirks for the distro. Unless there is a significant change to the build it would simplify things for anyone who struggles to build gdc (that doesn't require gdc in gcc though, just that there is a package).

It would certainly help having all distro quirks and dependencies dealth
with.
Having a very easy built process will help making more people use gdc and
help avoiding people like me :p


2011/9/23 Adam Burton <adz21c@gmail.com>

> dsimcha wrote:
> Once you have a package it's easy enough to `apt-get source`/download srpm,
> replace the code and rebuild producing new packages. rpm/apt-get makes sure
> you got all the dependencies and someone else has already tuned all the
> paths and any quirks for the distro. Unless there is a significant change
> to
> the build it would simplify things for anyone who struggles to build gdc
> (that doesn't require gdc in gcc though, just that there is a package).
>
>

== Quote from maarten van damme (maartenvd1994@gmail.com)'s article
> --0016e6d7e736ea5cfa04ada33393
> Content-Type: text/plain; charset=ISO-8859-1
> It would certainly help having all distro quirks and dependencies dealth
> with.
> Having a very easy built process will help making more people use gdc and
> help avoiding people like me :p

Actually, all distro quirks are internally maintained patches in the distribution, so nothing to do with GDC.  The easiest route would be just to obtain the source packages from your distributor and compile GDC using the same method.  All patches should still apply OK, and if they don't, let me know, and we can work together on that. :o)


This is needed in my zshrc file on Ubuntu:

LIBRARY_PATH=/usr/lib/i386-linux-gnu
CPATH=/usr/include/i386-linux-gnu
export LIBRARY_PATH CPATH


Regards
Iain