From: "Michael Ambrus" <ambrmi09@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sourceware.org
Subject: Re: Building SID
Date: Fri, 02 Mar 2007 14:18:00 -0000 [thread overview]
Message-ID: <81c474d20703020618l3806c167ib8d04a6fa94399d@mail.gmail.com> (raw)
In-Reply-To: <20070226185359.GC19131@redhat.com>
I synced the source just a minute ago, but the same compile problem is
still there. I had some time left to look at the issue.
Regarding SH, the problem relates to the sh2_cpu class in the sh2.h file:
class sh2_cpu: public
sh_compact_cpu<sh2_cpu,sh2_cpu_cgen,sh2_idesc,sh2_scache,sh_common_model<sh2_sh2_model,sh2_cpu,sh2_idesc,sh2_scache>
>
I didn't investigate further for now, but modified tconfig.in:
//#define SIDTARGET_SH @sidtarget_sh@
//#define SIDTARGET_SH64 @sidtarget_sh64@
That omits the SH target it seems.
Since I would like to try sid for more than one target (ARM and x86) I
tried to figure out if there would be an option for including all
targets *but* specific ones. The way sidtargets.m4 is written however,
it seems possible only to add targets explicitly. I'll see if I can
rewrite the logic so that both explicit inclusion and explicit
omission would be possible (i.e. something like
--disable-targets=<LIST> would be nice).
The build is then OK until component ARM is compiled.
Compiling the files arm.cxx and compTIMERS.cxx both give the same error:
/home/ambrmi09/projects/sid/src/sid/component/timers/arm7t/arm7t-timer.h:142:
error: looser throw specifier for 'virtual
armTimerNoSched::~armTimerNoSched()'
/home/ambrmi09/projects/sid/src/sid/component/timers/arm7t/arm7t-timer.h:70:
error: overriding 'virtual armTimer::~armTimer() throw ()'
I made the following change:
Index: sid/component/timers/arm7t/arm7t-timer.h
===================================================================
RCS file: /cvs/src/src/sid/component/timers/arm7t/arm7t-timer.h,v
retrieving revision 1.3
diff -r1.3 arm7t-timer.h
70c70
< ~armTimer() throw () { }
---
> ~armTimer() { throw (1); }
Have a look if the pach seems OK.
The build now succedes and I'm looking forward to try sid...
Best
/Michael
next prev parent reply other threads:[~2007-03-02 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 19:37 Michael Ambrus
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 [this message]
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=81c474d20703020618l3806c167ib8d04a6fa94399d@mail.gmail.com \
--to=ambrmi09@gmail.com \
--cc=fche@redhat.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).