On Wednesday, 2 March 2016 at 20:54:54 UTC, Iain Buclaw wrote:
On 2 Mar 2016 9:09 pm, "asdf via D.gnu"
wrote:
Are there build instructions that don't involve building the
rest of GCC
at the same time? I realize wrong version mismatches are bad
but I'll redo it until it works lol!
Sorry, no
On 2 Mar 2016 9:09 pm, "asdf via D.gnu" wrote:
>
> Are there build instructions that don't involve building the rest of GCC
at the same time? I realize wrong version mismatches are bad but I'll redo
it until it works lol!
Sorry, no. GCC isn't a library that you can just link to. You need to
bui
On 2016-03-02 07:47, asdf via D.gnu wrote:
> Are there build instructions that don't involve building the rest of GCC at
> the same time? I realize wrong version mismatches are bad but I'll redo it
> until it works lol!
I don't think so. Blame the legendary GCC modularity!
I wrote a simple scrip
Are there build instructions that don't involve building the rest
of GCC at the same time? I realize wrong version mismatches are
bad but I'll redo it until it works lol!
On Friday, 5 September 2014 at 15:49:22 UTC, Nordlöw wrote:
Have anyone put together a build script for
downloading/git-cloning and building a particular branch, say
gdc-4.9, of GDC?
Just throwing mine into the game:
Attention: it really cleans up the git repositories (cloned from
github) and
On 10 September 2014 21:58, Iain Buclaw wrote:
> On 9 September 2014 19:40, ketmar via D.gnu wrote:
>> On Mon, 8 Sep 2014 08:13:46 +0100
>> "Iain Buclaw via D.gnu" wrote:
>>
>> ok, i started. moved toDebug() and most of toDt() to visitor. yet
>> Expression::toElem() scares me alot (wow, it's 300
On 9 September 2014 19:40, ketmar via D.gnu wrote:
> On Mon, 8 Sep 2014 08:13:46 +0100
> "Iain Buclaw via D.gnu" wrote:
>
> ok, i started. moved toDebug() and most of toDt() to visitor. yet
> Expression::toElem() scares me alot (wow, it's 300kb!). but i hope to
> finish it in week or two (i have
On Mon, 8 Sep 2014 08:13:46 +0100
"Iain Buclaw via D.gnu" wrote:
ok, i started. moved toDebug() and most of toDt() to visitor. yet
Expression::toElem() scares me alot (wow, it's 300kb!). but i hope to
finish it in week or two (i have some free time now and can spend it on
porting).
i'm keeping p
On Mon, 8 Sep 2014 08:13:46 +0100
"Iain Buclaw via D.gnu" wrote:
> Doing these individual glue changes one at a time before 2.066-proper
> seems like a reasonable thing to do rather than trying to do all at
> once. And any patches to do such conversions would be welcome.
i tried to port lexer fr
On 5 September 2014 18:34, ketmar via D.gnu wrote:
> On Fri, 05 Sep 2014 17:23:22 +
> ""Nordlöw" via D.gnu" wrote:
>
>> Thanks! BTW: What's the current status on GDC in terms of
>> stability and DMD version? Is it at 2.065?
> 2.065 at the time of it's release, with all it's bugs and glory.
>
On Fri, 05 Sep 2014 17:23:22 +
""Nordlöw" via D.gnu" wrote:
> Thanks! BTW: What's the current status on GDC in terms of
> stability and DMD version? Is it at 2.065?
2.065 at the time of it's release, with all it's bugs and glory.
otherwise gdc is very stable; i'm using it as my primary compi
On Friday, 5 September 2014 at 17:23:24 UTC, Nordlöw wrote:
stability and DMD version? Is it at 2.065?
2.065 it is. I found it at
https://github.com/D-Programming-GDC/GDC/commit/2b2c781fe655139467f5260ae6ebd89c98ca1955
On Friday, 5 September 2014 at 16:47:27 UTC, Iain Buclaw via
D.gnu wrote:
https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/gdc
Thanks! BTW: What's the current status on GDC in terms of
stability and DMD version? Is it at 2.065?
On Fri, 05 Sep 2014 15:49:20 +
""Nordlöw" via D.gnu" wrote:
> Have anyone put together a build script for
> downloading/git-cloning and building a particular branch, say
> gdc-4.9, of GDC?
yes, i'm using such script. ;-)
signature.asc
Description: PGP signature
On 5 September 2014 16:49, "Nordlöw" via D.gnu wrote:
> Have anyone put together a build script for downloading/git-cloning and
> building a particular branch, say gdc-4.9, of GDC?
This is the closest thing I know of to an actual script, whilst not
strictly being complete or anything.
https://pr
Have anyone put together a build script for
downloading/git-cloning and building a particular branch, say
gdc-4.9, of GDC?
On 31 October 2013 18:38, Steve Teale wrote:
> On Thursday, 31 October 2013 at 17:33:52 UTC, Steve Teale wrote:
>
>> Mea Culpa.
>>
>> In attempting to install the prerequisites
>>
>> libmpc-dev
>> libmpfr-dev
>> libgmp3-dev
>>
>> I ended up building from the source code for these projects.
>>
>>
On 31/10/13 19:38, Steve Teale wrote:
My recipe can be found at britseyeview.com/software/buildGDC.txt
I hope this will save others some grief.
Nice writeup! :-)
One thing -- about tweaking the PATH variable -- I find it useful to have a
little script for this, /etc/profile.d/opt.sh :
for
On Thursday, 31 October 2013 at 17:33:52 UTC, Steve Teale wrote:
Mea Culpa.
In attempting to install the prerequisites
libmpc-dev
libmpfr-dev
libgmp3-dev
I ended up building from the source code for these projects.
Later, back to square one, I simply installed them using
apt-get.
Then the
On Thu, Oct 31, 2013 at 06:33:50PM +0100, Steve Teale wrote:
> Mea Culpa.
>
> In attempting to install the prerequisites
>
> libmpc-dev
> libmpfr-dev
> libgmp3-dev
>
> I ended up building from the source code for these projects.
>
> Later, back to square one, I simply installed them using apt-g
On 31/10/13 18:33, Steve Teale wrote:
Mea Culpa.
Don't worry about it. It's always good to know how builds can go wrong for
people, because that helps the next person who runs into difficulty. Glad you
finally got it built! :-)
Mea Culpa.
In attempting to install the prerequisites
libmpc-dev
libmpfr-dev
libgmp3-dev
I ended up building from the source code for these projects.
Later, back to square one, I simply installed them using apt-get.
Then the build worked.
Grovel, grovel, my apologies to those whose time I wa
On 31/10/13 13:45, Steve Teale wrote:
There are xgcc errors, and a shared library for MPFR that can't be found.
This is a guess, but ... as it looks like the build process might be being
incorrectly configured, are there any warnings in the log about needing
different versions of automake, et
On Thursday, 31 October 2013 at 12:49:38 UTC, Joseph Rushton
Wakeling wrote:
On 31/10/13 13:07, Steve Teale wrote:
$CPATH and $LIBRARY_PATH were initially empty, and the build
failed as decribed.
I set them to the paths above, and the build failed in the
same way.
Did you try my detailed list
Supposing that you're using $SOMEDIR/gdc to store everything, a
rough description of the procedure would be:
* Clone GDC master into gdc/dev
* Unzip the GCC source into gdc, which will give you a
subdirectory
called gcc-$VERSION (currently gcc-4.8.2)
* cd into gdc/dev and
On 31/10/13 13:07, Steve Teale wrote:
$CPATH and $LIBRARY_PATH were initially empty, and the build failed as decribed.
I set them to the paths above, and the build failed in the same way.
Did you try my detailed list of instructions for building using GCC 4.8 sources?
On Thursday, 31 October 2013 at 11:54:14 UTC, Joseph Rushton
Wakeling wrote:
On 31/10/13 12:46, Alexandr Druzhinin wrote:
Ubuntu 12.04 x86_64 user here, I build gdc 4.8.1 following
instructions I link
above without issues, so I don't know what to do - but I'm
sure it's possible :)
P.S. I have
On Thursday, 31 October 2013 at 11:46:25 UTC, Alexandr Druzhinin
wrote:
31.10.2013 18:36, Steve Teale пишет:
On Thursday, 31 October 2013 at 10:45:05 UTC, Joseph Rushton
Wakeling
wrote:
On 31/10/13 11:31, Steve Teale wrote:
so possibly the MPFR install put it in the wrong place. I
will look
On 31/10/13 12:46, Alexandr Druzhinin wrote:
Ubuntu 12.04 x86_64 user here, I build gdc 4.8.1 following instructions I link
above without issues, so I don't know what to do - but I'm sure it's possible :)
P.S. I have mpfr in /usr/lib/x86_64-linux-gnu/
In my case the 12.04 build platform was 64
On 31/10/13 12:36, Steve Teale wrote:
On Thursday, 31 October 2013 at 10:45:05 UTC, Joseph Rushton Wakeling wrote:
On 31/10/13 11:31, Steve Teale wrote:
so possibly the MPFR install put it in the wrong place. I will look for it.
Where is the right place?
What OS are you running?
Ubuntu 12.0
31.10.2013 18:36, Steve Teale пишет:
On Thursday, 31 October 2013 at 10:45:05 UTC, Joseph Rushton Wakeling
wrote:
On 31/10/13 11:31, Steve Teale wrote:
so possibly the MPFR install put it in the wrong place. I will look
for it.
Where is the right place?
What OS are you running?
Ubuntu 12.04
On Thursday, 31 October 2013 at 10:45:05 UTC, Joseph Rushton
Wakeling wrote:
On 31/10/13 11:31, Steve Teale wrote:
so possibly the MPFR install put it in the wrong place. I will
look for it.
Where is the right place?
What OS are you running?
Ubuntu 12.04
Hello Steve,
It's been a while since you've poked your head round here. ;-)
This error message you are getting is quite misleading and
frequently the
problem has nothing to do with the message. You have to check
the file
'config.log' in the directory where the error occurred. In the
erro
On 31/10/13 11:31, Steve Teale wrote:
so possibly the MPFR install put it in the wrong place. I will look for it.
Where is the right place?
What OS are you running?
On 31/10/13 09:59, Iain Buclaw wrote:
In Ubuntu, even if these packages are installed, they are put into multiarch
directories which vanilla GCC isn't aware of.
Has not been my experience for GCC 4.8+. I don't think I have any custom CPATH
or LPATH settings on my Ubuntu 13.10 system.
OK, got all the tools installed and the build for GDC went on
for some
time, but eventually bombed out with:
checking for suffix of object files... configure: error: in
`/home/steve/gdc/objdir/i686-**pc-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files:
cannot compile
On 31 October 2013 08:34, Steve Teale wrote:
> On Wednesday, 30 October 2013 at 06:18:02 UTC, Alexandr Druzhinin wrote:
>
>> 30.10.2013 11:58, Steve Teale пишет:
>>
>>> I want to build gtkD. For that I need a version 2 GDC. Ubuntu is still
>>> on V2.
>>>
>>> Are there any clear build instructions
On Wednesday, 30 October 2013 at 06:18:02 UTC, Alexandr Druzhinin
wrote:
30.10.2013 11:58, Steve Teale пишет:
I want to build gtkD. For that I need a version 2 GDC. Ubuntu
is still
on V2.
Are there any clear build instructions available, or even a
binary ;=)
http://gdcproject.org/wiki/Install
30.10.2013 11:58, Steve Teale пишет:
I want to build gtkD. For that I need a version 2 GDC. Ubuntu is still
on V2.
Are there any clear build instructions available, or even a binary ;=)
http://gdcproject.org/wiki/Installation/General to build from source.
Binary exists, but it's better to build
I want to build gtkD. For that I need a version 2 GDC. Ubuntu is
still on V2.
Are there any clear build instructions available, or even a
binary ;=)
On Mon, Oct 22, 2012 at 09:29:01AM -0700, H. S. Teoh wrote:
> On Mon, Oct 22, 2012 at 07:48:52AM +0200, Timo Sintonen wrote:
> > On Sunday, 21 October 2012 at 13:14:25 UTC, Iain Buclaw wrote:
> >
> > >If you compiled gdc - it should have also include libphobos in the
> > >build... unless you did s
On Mon, Oct 22, 2012 at 07:48:52AM +0200, Timo Sintonen wrote:
> On Sunday, 21 October 2012 at 13:14:25 UTC, Iain Buclaw wrote:
>
> >If you compiled gdc - it should have also include libphobos in the
> >build... unless you did something strange and omitted it. :)
>
> The old update script did it
On Sunday, 21 October 2012 at 13:14:25 UTC, Iain Buclaw wrote:
If you compiled gdc - it should have also include libphobos in
the
build... unless you did something strange and omitted it. :)
The old update script did it wrong sometimes. When the sources
were parallel, like /usr/local/src/gcc
On 21 October 2012 21:31, Brad Lanam wrote:
> On Saturday, 20 October 2012 at 05:37:20 UTC, H. S. Teoh wrote:
>>
>> configure: error: Link tests are not allowed after
>> GCC_NO_EXECUTABLES.
>
>
> Had this problem many, many times...
> IIRC I think this is the piece you need, which isn't do
On Saturday, 20 October 2012 at 05:37:20 UTC, H. S. Teoh wrote:
configure: error: Link tests are not allowed after
GCC_NO_EXECUTABLES.
Had this problem many, many times...
IIRC I think this is the piece you need, which isn't documented
well.
if [[ $(uname -m) == "x86_64" ]]; then
export L
On 20 October 2012 18:14, H. S. Teoh wrote:
> Huh, weird, I tried compiling again this morning and somehow it works
> now!! I think it may have to do with the configure options: I tried a
> different configuration this time:
>
> /usr/src/gcc-4.7/gcc-4.7-4.7.2/src/configure \
> --en
Huh, weird, I tried compiling again this morning and somehow it works
now!! I think it may have to do with the configure options: I tried a
different configuration this time:
/usr/src/gcc-4.7/gcc-4.7-4.7.2/src/configure \
--enable-languages=d --disable-bootstrap \
--prefix=
On Sat, Oct 20, 2012 at 08:38:23AM +0200, Timo Sintonen wrote:
[...]
> To make an executable we need headers, a working compiler, working
> binutils and working libraries for the target system. Even if the
> target system is the same ( I assume you are not making a
> cross-compiler) configure may g
I can not help you in this case, but this is a general problem in
compiling gcc package, specially when making a cross compiler.
The message is a bit misleading and is not related to the test
which generates it.
Somewhere at the beginning, configure tests if it is possible to
compile and link a
Hi all,
I spent almost the whole day trying to get GDC to build on my 64-bit
Debian system, only to fail miserably. Are there any steps /
configurations that are known to work??
Here's what I figured out so far: Debian's multiarch directory structure
breaks the pristine gcc sources (due to stuff
This did not help with my particular issue.
For some reason I'm getting those cross-compile errors.
Are there any CFLAGS you use?
I've tried building w/gcc-4.6.1 and gcc-4.4.6.
No. I only needed to set these 2 variables to make it work on Ubuntu 11.10
export $CPATH=/usr/include/x86_64-linux-gnu
Of course it's
export CPATH=/usr/include/x86_64-linux-gnu
Trass3r Wrote:
> export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
> export $CPATH=/usr/include/x86_64-linux-gnu
Thanks for the reply.
This did not help with my particular issue.
For some reason I'm getting those cross-compile errors.
Are there any CFLAGS you use?
I've tried building w/gcc-4.6.1
export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
export $CPATH=/usr/include/x86_64-linux-gnu
Does anyone know how to get gdc to build on a 64-bit linux machine?
I can build gdc on linuxmint11 (32-bit) and gdc v2 on FreeBSD 8.2 (32-bit).
I have included below the script I use.
I've tried removing "." from PATH; I've tried --enable-multilib and
--disable-multilib.
The error I get is:
check
No matter how hard I try, I find myself unable to build GDC (D2, GCC
4.5.2) by following the directions at:
https://bitbucket.org/goshawk/gdc/wiki/MinGWCompile
I'm on Win7/64bit. Is there some sort of directions that I can follow or
something I'm missing? It will always error out in the middle of
Don wrote:
> I really want to use D but I'm constantly frustrated by issues just
> like this.
>
> I get the same error message on 64 bit Ubunutu 10.10 as well.
>
Have you tried adding "CC=$(which gcc)" to your configure
command line?
Jerome
--
mailto:jeber...@free.fr
htt
Don wrote:
> I really want to use D but I'm constantly frustrated by issues just
> like this.
>
> I get the same error message on 64 bit Ubunutu 10.10 as well.
>
> I do plan to stick with it and when D is within 5% of the speed of gcc
> for my type of application (computer chess) I'm switching.
Trass3r wrote:
> What about Iain's ppa: https://launchpad.net/~ibuclaw/+archive/ppa
I've not tested it but these looks like D1 packages rather than D2 (based on
the contents of std in libphobos packages).
What about Iain's ppa: https://launchpad.net/~ibuclaw/+archive/ppa
I really want to use D but I'm constantly frustrated by issues just
like this.
I get the same error message on 64 bit Ubunutu 10.10 as well.
I do plan to stick with it and when D is within 5% of the speed of gcc
for my type of application (computer chess) I'm switching.
Sorry I cannot be of more
Jérôme M. Berger Wrote:
> I am going to take a bet that you have "." in your path. If that is
> the case, you need to add "CC=$(which gcc)" to your configure
> command line (and it is not something you are doing wrong, it is a
> bug in gcc).
That worked!
Jérôme, you are a star! Thank yo
edam wrote:
> Hi there,
>
> I'm trying to follow the instructions at
> https://bitbucket.org/goshawk/gdc/wiki/Home to build GDC from the mercurial
> repos, but I've not been successful. Not being familiar with the GCC build
> process myself, I was wondering if anyone could shed a bit of light o
Hi there,
I'm trying to follow the instructions at
https://bitbucket.org/goshawk/gdc/wiki/Home to build GDC from the mercurial
repos, but I've not been successful. Not being familiar with the GCC build
process myself, I was wondering if anyone could shed a bit of light on the
problem?
I shoul
64 matches
Mail list logo
