public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Ambrus" <ambrmi09@gmail.com>
To: sid@sourceware.org
Subject: Building SID
Date: Sun, 25 Feb 2007 19:37:00 -0000	[thread overview]
Message-ID: <81c474d20702251137j3e65f89aidf58a2e4cf019252@mail.gmail.com> (raw)

Hi,
I'm new to sid and I'm having some problems building the project from
CVS sources.

My first attempt was with a cross-compiler which worked. except that
the I couldn't get the simulation to work properly (when setting CPU
registers in the simulated code and then queried the same with GDB,
the registers would still have the value 0). I thought if not setting
--target, it would make it work better. The documentation says that if
--target is not set, sid will try to build all the available CPU's.

What I'm not clear about is if one needs a cross compilers or not, and
in the case one does - would that be for every possible CPU sid
supports?

If cross compilers are meant to be used, which name should one use for
--target? I'm confused over that the canonical name for an x86
tool-chain normally would be i[[3456789]]86-*-*, but sid seems to use
the name x86 (or at least for the component i.e.).

A list of supported main architectures would be helpful.

Hers comes the lines where the build breaks:

make[4]: Entering directory `/home/ambrmi09/projects/sid/_BUILD/sid/bsp'
make[4]: *** No rule to make target `sh64-elf-sid', needed by `all-am'.  Stop.
make[4]: Leaving directory `/home/ambrmi09/projects/sid/_BUILD/sid/bsp'

The directory is there, but there's no trace of sh64. The ones existing:

arm-elf-sid
i386-elf-sid
m32r-elf-sid
  m68k-elf-sid
mt-elf-sid
xstormy16-elf-sid

The ChangeLog mentions  'sh-elf-sid,sh5-elf-sid,sh64-elf-sid: New
files' so I'm guessing the files were just not committed yet.

Regards
/Michael Anbrus

             reply	other threads:[~2007-02-25 19:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 19:37 Michael Ambrus [this message]
2007-02-26  0:21 ` Frank Ch. Eigler
2007-02-26  0:45   ` Michael Ambrus
2007-02-26 18:54     ` Frank Ch. Eigler
2007-02-26 19:42       ` Michael Ambrus
2007-03-02 14:18       ` Michael Ambrus
2007-03-02 15:58         ` Dave Brolley
2007-03-02 16:31           ` Michael Ambrus
2007-03-02 17:22             ` Frank Ch. Eigler
2007-03-02 18:00               ` Michael Ambrus
2007-03-02 18:11                 ` Frank Ch. Eigler
2007-03-02 18:22                   ` Michael Ambrus
2007-03-02 18:45                     ` Dave Brolley
2007-03-02 20:03                       ` Michael Ambrus
     [not found]                   ` <20070303011808.GC18185@redhat.com>
     [not found]                     ` <81c474d20703030457j3775edd7x78211179d3f6d62e@mail.gmail.com>
     [not found]                       ` <20070303143422.GD18185@redhat.com>
     [not found]                         ` <81c474d20703030639i40a30aa4v6a01be2e4160e4cd@mail.gmail.com>
     [not found]                           ` <20070303144102.GF18185@redhat.com>
     [not found]                             ` <81c474d20703030700k2b8d4b32h9e323f0bb8ce90a7@mail.gmail.com>
     [not found]                               ` <20070303163018.GG18185@redhat.com>
     [not found]                                 ` <81c474d20703050549n3577b589gdeccea3db5f33ae7@mail.gmail.com>
     [not found]                                   ` <20070305173328.GA8990@redhat.com>
2007-03-05 22:09                                     ` Michael Ambrus
2007-03-05 22:50                                       ` Frank Ch. Eigler
2007-03-02 17:12           ` Dave Brolley
2007-02-26 16:26   ` Dave Brolley
2007-02-26 17:51     ` Michael Ambrus
2007-02-26 18:54       ` Dave Brolley
2007-02-26 19:12         ` Michael Ambrus

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=81c474d20702251137j3e65f89aidf58a2e4cf019252@mail.gmail.com \
    --to=ambrmi09@gmail.com \
    --cc=sid@sourceware.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).