From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Andrew Dean <Andrew.Dean@microsoft.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: How to test aarch64 when building a cross-compiler?
Date: Mon, 25 Nov 2019 21:55:00 -0000 [thread overview]
Message-ID: <CAJA7tRacm141sc5KvMWs8KdwdCMfacViJz-f_5FR242KpNhm-w@mail.gmail.com> (raw)
In-Reply-To: <CO2PR00MB01177DD4434CAD4691020200EA4A0@CO2PR00MB0117.namprd00.prod.outlook.com>
On Mon, Nov 25, 2019 at 9:43 PM Andrew Dean <Andrew.Dean@microsoft.com> wrote:
>
> > > >>> I get errors like this:
> > > >>>
> > > >>> aarch64-glibc-linux-gnu-gcc: fatal error: cannot read spec file
> > > >>> 'rdimon.specs': No such file or directory
> > > >>>
> > > >>> I can see that the rdimon.specs flag is added based on this line
> > > >>> in aarch64-
> > > >> sim.exp:
> > > >>
> > > >> Where does aarch64-sim.exp comes from?
> > > >
> > > > /usr/share/dejagnu/baseboards/aarch64-sim.exp
> > > >
> > > >>
> > > >>>
> > > >>> set_board_info ldflags "[libgloss_link_flags] [newlib_link_flags]
> > > >>> -
> > > >> specs=rdimon.specs"
> > > >>>
> > > >> I think this is for baremetal/newlib targets, ie. aarch64-elf, not
> > > >> for aarch64- linux-gnu.
> > > >
> >
> > Yes -specs=rdimon.specs and other such flags are for use only on bare-metal
> > targets.
> >
> > > > Hmm.. build-many-glibcs.py doesn't like either aarch64-elf or aarch64-linux-
> > elf...
> > > > I get a KeyError in build_compilers and build_glibcs when it tries to look up
> > the config with either of those values.
> > > >
> > >
> > > Unfortunately the build-many-glibcs.py does not have support for
> > > baremetal build yet (since it is a tool created to build
> > > cross-compiling toolchain using glibc).
> >
> > And glibc doesn't work bare-metal ......
> >
> > regards
> > Ramana
> I guess that means that the dejagnu baseboard "aarch64-sim" is only meant to do bare-metal testing? How would one build/test GCC hosted on x86_64 and targeting aarch64 then? Is there a different simulator approach I should be using?
For cross-compilers with Linux, you've got 2 options - write up a
board file to use qemu in user-emulation mode or indeed system
emulation mode or use real hardware and construct something using ssh
/ scp.
R
next prev parent reply other threads:[~2019-11-25 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:17 Andrew Dean via gcc
2019-11-25 20:16 ` Christophe Lyon
2019-11-25 20:28 ` [EXTERNAL] " Andrew Dean via gcc
2019-11-25 20:40 ` Adhemerval Zanella
2019-11-25 20:44 ` Ramana Radhakrishnan
2019-11-25 21:43 ` Andrew Dean via gcc
2019-11-25 21:55 ` Ramana Radhakrishnan [this message]
2019-11-26 20:53 ` Jeff Law
2019-11-27 20:21 ` Andrew Dean via gcc
2019-11-27 20:42 ` Andreas Schwab
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=CAJA7tRacm141sc5KvMWs8KdwdCMfacViJz-f_5FR242KpNhm-w@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=Andrew.Dean@microsoft.com \
--cc=adhemerval.zanella@linaro.org \
--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).