From: Andi Hellmund <mail@andihellmund.com>
To: charfi asma <charfiasma@yahoo.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: can not make gcc-dev
Date: Thu, 17 Feb 2011 18:15:00 -0000 [thread overview]
Message-ID: <4D5D581C.6070105@andihellmund.com> (raw)
In-Reply-To: <307075.68480.qm@web28506.mail.ukl.yahoo.com>
Hey Asma,
> I tried to install gcc that I get from git clone
> git://crules.org/git/gcc-dev.git.
>
It seems that this repo is not totally up-to-date. The GIT logs show
that the last update apparently was on Feb 15, but Phil will now this
better. Anyway, you could also the following ways to get the GCC trunk:
via GIT: http://gcc.gnu.org/wiki/GitMirror
via SVN: http://gcc.gnu.org/svn.html
> I configure with : ../gcc-dev/configure --enable-languages=c,c++,uml
> --disable-werror --disable-bootstrap
>
> when I call make with: make STAGE1_CFLAGS="g -O1" I get those errors msg
> dealing with lexer and parser !!
>
I'm not sure if that works if you disable bootstrapping, because I think
that staging is only relevant for bootstap builds. Instead, you could
just use CFLAGS. Another note: if you plan to build a debugable version
of gcc (it seems so due to the -O1 option), I personally favor to add
-fno-inline as well.
> ......
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:915:
> undefined reference to `lexer_line'
> build/gengtype-parse.o: In function `token':
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:49:
> undefined reference to `yylex'
> build/gengtype-parse.o: In function `typedef_decl':
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:838:
> undefined reference to `lexer_line'
> build/gengtype-parse.o: In function `def_vec_alloc':
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:939:
> undefined reference to `lexer_line'
> build/gengtype-parse.o: In function `token':
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:49:
> undefined reference to `yylex'
> /export/home/charfi/Bureau/build_uml/gcc/../../gcc-dev/gcc/gengtype-parse.c:49:
> undefined reference to `yylex'
> collect2: ld a retourné 1 code d'état d'exécution
> make[2]: *** [build/gengtype] Erreur 1
> make[2]: quittant le répertoire « /export/home/charfi/Bureau/build_uml/gcc »
> make[1]: *** [all-gcc] Erreur 2
> make[1]: quittant le répert
>
>
I don't know why you get this error. Let me try to check on my system.
Anyway, I would first try to get the really latest bits and try again on
your system ...
Best regards,
Andre-Marcel
next prev parent reply other threads:[~2011-02-17 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 16:53 charfi asma
2011-02-17 18:15 ` Andi Hellmund [this message]
2011-02-17 18:33 ` Jonathan Wakely
2011-02-17 19:32 ` Andi Hellmund
2011-02-18 1:13 ` Philip Herron
2011-02-18 14:13 ` Re : " charfi asma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5D581C.6070105@andihellmund.com \
--to=mail@andihellmund.com \
--cc=charfiasma@yahoo.fr \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).