This is the mail archive of the
mailing list for the SID project.
- From: "Michael Ambrus" <ambrmi09 at gmail dot com>
- To: sid at sourceware dot org
- Date: Sun, 25 Feb 2007 20:37:41 +0100
- Subject: Building SID
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=bQLTsI8qPIHreMdFRfPMTIeOooDL45HZ/vIJwV6JAgfi2hwTzn6d0EnH+eR3hMfibdurgPPQeKV6/SBLUFTIp7agGyjTITaV2jV35I2/wJ2+/Q188z+Ouf+UiqCc8y6JX0M45n3vtGxkVsEPd48Y864ZbvqtecEIt7gzr4/zf1w=
I'm new to sid and I'm having some problems building the project from
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
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[]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: Entering directory `/home/ambrmi09/projects/sid/_BUILD/sid/bsp'
make: *** No rule to make target `sh64-elf-sid', needed by `all-am'. Stop.
make: Leaving directory `/home/ambrmi09/projects/sid/_BUILD/sid/bsp'
The directory is there, but there's no trace of sh64. The ones existing:
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.