From: Mateus Carmo Martins de Freitas Barbosa <mateus.carmo.barbosa@usp.br>
To: gcc@gcc.gnu.org
Subject: Rust front-end
Date: Fri, 23 Aug 2019 14:11:00 -0000 [thread overview]
Message-ID: <CACeY_ch4cPydJv5BV63j5A5NrR254a9a-=V+g3wcLPTaLhiM0g@mail.gmail.com> (raw)
I'm interested in working on the Rust front-end for GCC.
So far I've cloned the repository <https://github.com/redbrain/gccrs.git>
and tried to compile it as described in <https://gcc.gnu.org/wiki/RustFrontEnd>.
I've compiled it outside of the gcc directory tree with
$ ../gccrs/configure --prefix=/opt/gccrs --enable-languages=rust
--disable-multilib --disable-bootstrap
$ make
But this produces some linking errors for functions that were called
but never defined:
/usr/bin/ld: rust/rust-lang.o: in function
`rust_langhook_handle_option(unsigned long, char const*, long, int,
unsigned int, cl_option_handlers const*)':
/home/baal/gccrs-build/gcc/../../gccrs/gcc/rust/rust-lang.c:185:
undefined reference to `rust_add_search_path(char const*)'
/usr/bin/ld: /home/baal/gccrs-build/gcc/../../gccrs/gcc/rust/rust-lang.c:213:
undefined reference to `rust_add_search_path(char const*)'
/usr/bin/ld: /home/baal/gccrs-build/gcc/../../gccrs/gcc/rust/rust-lang.c:217:
undefined reference to `rust_add_search_path(char const*)'
/usr/bin/ld: rust/rust-lang.o: in function `rust_langhook_post_options':
/home/baal/gccrs-build/gcc/../../gccrs/gcc/rust/rust-lang.c:245:
undefined reference to `rust_add_search_path(char const*)'
/usr/bin/ld: rust/rust-lang.o: in function `rust_langhook_parse_file()':
/home/baal/gccrs-build/gcc/../../gccrs/gcc/rust/rust-lang.c:282:
undefined reference to `rust_parse_input_files(char const**, unsigned
int, bool)'
/usr/bin/ld: rust/rust-lang.o:/home/baal/gccrs-build/gcc/./gtype-rust.h:24:
undefined reference to `rust_non_zero_struct'
collect2: error: ld returned 1 exit status
make[2]: *** [../../gccrs/gcc/rust/Make-lang.in:61: rust1] Error 1
make[2]: Leaving directory '/home/baal/gccrs-build/gcc'
make[1]: *** [Makefile:4319: all-gcc] Error 2
It's doesn't really help that the latest commit message
(3b1e76d808b9725e6ef439ae534011370e65fb85) says simply "x" and the
previous one, only "more". Anyhow, I'm left with those questions:
- Considering I'm new to gcc development, what should I read before
getting into this?
- Is there any developer in particular I should talk to?
- Is there anything else I need to know before getting started?
next reply other threads:[~2019-08-23 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 14:11 Mateus Carmo Martins de Freitas Barbosa [this message]
2019-08-27 8:10 ` Bin.Cheng
2019-08-27 9:34 ` Jonathan Wakely
2019-08-27 14:58 ` David Malcolm
2019-08-30 20:24 ` Mateus Carmo Martins de Freitas Barbosa
2022-06-27 14:51 Philip Herron
2022-06-28 7:30 ` Richard Biener
2022-07-08 17:31 ` Philip Herron
2022-07-11 7:50 ` Richard Biener
2022-07-11 15:01 ` David Edelsohn
2022-10-04 12:29 ` Philip Herron
2022-10-04 12:42 ` David Malcolm
2022-10-04 13:04 ` Jakub Jelinek
2022-10-05 9:39 ` Philip Herron
2022-10-05 9:36 ` Philip Herron
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='CACeY_ch4cPydJv5BV63j5A5NrR254a9a-=V+g3wcLPTaLhiM0g@mail.gmail.com' \
--to=mateus.carmo.barbosa@usp.br \
--cc=gcc@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).