[GCC front end] trying to install sample_fe but fail in make

[Philip Herron]

Hey

On 23 June 2010 23:41, Andi Hellmund <mail@andihellmund.com> wrote:
> * you mentioned that the config-lang.in file from the C++ front-end works
> without any problems even though both files, from the C++ front-end and the
> sample_fe front-end "look" equal. But maybe, something went wrong during the
> download or extraction of the archive (just for the case, here's a checksum
> of the file using the cksum utility
>
> sample_fe config-lang.in
> 1684117529 427 config-lang.in

Maybe his shell doesnt like the _ in sample_fe but i doubt it not
really sure whats going on with his code.

>
> * alternatively (a bit more time-consuming), you could try to copy the
> config-lang.in from the C++ front-end to the sample_fe directory and
> successively change this file back to the contents of the sample_fe
> config-lang.in while checking which change really makes the problems
>
> * if that all doesn't help, you could try to follow the suggestion of Philip
> to use his code for the python front-end with gcc-4.5.0
>

I think really if you really want to build a front-end is start
working with llive GCC sources since we will be able to help you more
easily than trying to debug whats going on with building it in older
versions of GCC.

I really think you should just start from scratch here and:

mkdir gcc-dev && cd gcc-dev
git clone git://gcc.gnu.org/git/gcc.git
cd gcc
mkdir build
../configure --enable-languages=c,c++,fortran
make
sudo make install

If this all works fine were on our way.

Then you need to understand a little bit about GCC, the driver and
compiler proper. We build a compiler driver which decides which
compiler to invoke over an input.

So if you go into the gcc folder and look for a language like fortran
this is all its front-end specific code, and there is gfortranspec.c
which is this compiler driver then there is bla-lang.c is the compiler
proper is the naming convention.

The config-lang.in just denotes some config options like your lang
name your compiler executable and your runtime library name etc.

Then your Make-lang.in is your makefile for this setup. I am not going
to lie the documentation for building up your front-end is nearly
non-existant but we are working on this too, but there is alot to
document. And it requires good understanding on C and Compiler
construction overall. I would say take look at my front-end and the
gccgo front-end they are the most readable front-ends since they lack
the maturity of once's like C and Fortran or Ada which are fairly
difficult to read.

--Phil