From: Dave Brolley <brolley@redhat.com>
To: Michael Ambrus <ambrmi09@gmail.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, sid@sourceware.org
Subject: Re: Building SID
Date: Mon, 26 Feb 2007 18:54:00 -0000 [thread overview]
Message-ID: <45E32CC0.8080901@redhat.com> (raw)
In-Reply-To: <81c474d20702260951ub995838w7c359687fdc62fc8@mail.gmail.com>
Michael Ambrus wrote:
> I've got the files thanx. They seem broken however....
>
> The following is the first place where it breaks (I noticed that the
> build system will not respect neither 'make -S' nor 'export
> MAKEFLAGS="-S" && make' - it seems that the recursive build is using
> 'make -k' no matter what I do).
>
> ../../../../src/sid/component/cgen-cpu/sh/sh2.h:16: error:
> 'sh_common_model' was not declared in this scope
> ../../../../src/sid/component/cgen-cpu/sh/sh2.h:16: error: wrong
> number of template arguments (8, should be 5)
Compiles fine for me using
>> gcc --version
gcc (GCC) 4.1.2 20060612 (prerelease) (GNUPro 06r1)
I can't tell for sure, because I don't know which file you were
compiling at the time, but it looks to me like sh_common_model is in the
global namespace, so I'm not sure why it can't be found. Perhaps a
'using namespace ::'
is needed before the declaration of sh2_cpu?
> :
> :
> Which leads to this:
>
> :
> :
> ../../../../src/sid/component/cgen-cpu/sh/sh4-nofpu-defs.h:22: error:
> forward declaration of 'class sh4_nofpu::sh4_nofpu_cpu'
This forward declaration is intentional. Any idea why it would not be
allowed?
> gcc used is the native one for my system which is i486-linux-gnu
> (version 4.0). Note that the standard for forward declarations to
> templates has changed (in case you're using an older compiler).
>
next prev parent reply other threads:[~2007-02-26 18:54 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
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 [this message]
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=45E32CC0.8080901@redhat.com \
--to=brolley@redhat.com \
--cc=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).