public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gregg Levine" <gregg.drwho8@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Strange errors when building Redboot for the SH/Dreamcast platform
Date: Sun, 18 Jun 2006 03:24:00 -0000	[thread overview]
Message-ID: <18d205ed0606172024y217b51cdk6871fb734e5ed4e3@mail.gmail.com> (raw)
In-Reply-To: <18d205ed0606170908m58f29749o6d6412ddd0133294@mail.gmail.com>

Hello!
An update.
About an hour, to three hours ago, I moved my build setup from my
Cygwin system to my Linux system. It seems it worked there, but not on
my Cygwin system. I don't know why.

Oh and Andrew, by default you do mean everything? I typically select
Redboot first, and see if the resulting image will boot on the target.
And then when ready start building the kernel and other libraries.
Perhaps this time the target will include an entire program to do
something unique. Just for the record, the graphic configure tool
looks for the version 2 PNG library, and my Slackware 10.1 system came
with the 3.1.2.0 version. I made a link to that library with the named
one as the link and it worked. Next step will be to test that Redboot
image. And finally to work out how to perform the tests. I think I've
got an idea how to do that.
-- 
Gregg C Levine gregg.drwho8@gmail.com
"This signature was once found posting rude
 messages in English in the Moscow subway."


On 6/17/06, Gregg Levine <gregg.drwho8@gmail.com> wrote:
> Hello!
> Andrew, I don't understand your first post and do understand your
> second. That was the default Redboot configuration. About all I did
> was make sure and choose to answer the questions asked about what
> CYGMON settings should be chosen.
>
>  And as for what platform its being built for, I made sure of that too.
> --
> Gregg C Levine gregg.drwho8@gmail.com
> "This signature was once found posting rude
>  messages in English in the Moscow subway."
>
>
> On 6/17/06, Andrew Lunn <andrew@lunn.ch> wrote:
> > On Sat, Jun 17, 2006 at 10:00:03AM +0200, Andrew Lunn wrote:
> > > On Fri, Jun 16, 2006 at 11:50:07PM -0400, Gregg Levine wrote:
> > > > Hello!
> > > > I am back with the issues of building eCos and Redboot and all of that
> > > > for the Dreamcast platform. It seems even though I checked out the
> > > > entire repository just about two or more hours ago, and updated the
> > > > configuration tools accordingly a problem surfaced.
> > >
> > > sh-elf-gcc -finline-limit=7000 -ml -m3 -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -ggdb -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions    -I/ecos-c/cygwin/usr/local/dc/ecos/test1_install/include -I/usr/local/anoncvs/ecos/packages/hal/sh/arch/current -I/usr/local/anoncvs/ecos/packages/hal/sh/arch/current/src -I/usr/local/anoncvs/ecos/packages/hal/sh/arch/current/tests -I. -Wp,-MD,sh_offsets.tmp -o hal_mk_defs.tmp -S /usr/local/anoncvs/ecos/packages/hal/sh/arch/current/src/hal_mk_defs.c
> > >
> > > In file included from /usr/local/anoncvs/ecos/packages/hal/sh/arch/current/src/hal_mk_defs.c:57:
> > >
> > > /ecos-c/cygwin/usr/local/dc/ecos/test1_install/include/cyg/hal/hal_arch.h:60:10: #include expects "FILENAME" or <FILENAME>
> > >
> > > First logical question i ask myself. What is line 60 of
> > > /hal/hal_arch.h?
> > >
> > > I guess it is probably something like
> > >
> > > #include CYGBLD_SOME_HEADER_FILE
> > >
> > > So the next logical questions are, why does CYGBLD_SOME_HEADER_FILE not
> > > have a value? Where is it supposed to be defined etc....
> >
> > FYI:
> >
> > :~/eCos/work2$ rm -fr *
> > :~/eCos/work2$ ecosconfig new dreamcast redboot
> > U CYGPKG_HAL_SH_7750, new inferred value 1
> > U CYGHWR_HAL_SH_CACHE_ENABLE, new inferred value 0
> > U CYGDAT_REDBOOT_SH_LINUX_BOOT_ENTRY, new inferred value 0x8C210000
> > U CYGDAT_REDBOOT_SH_LINUX_BOOT_BASE_ADDR, new inferred value 0x8C001000
> > U CYGDAT_REDBOOT_SH_LINUX_BOOT_COMMAND_LINE, new inferred value mem=16M
> > U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
> > :~/eCos/work2$ ecosconfig tree
> > :~/eCos/work2$ make -s
> > headers finished
> > /home/lunn/eCos/anoncvs-clean/packages/hal/sh/dreamcast/current/src/fb_support.c: In function `lcd_clear':
> > /home/lunn/eCos/anoncvs-clean/packages/hal/sh/dreamcast/current/src/fb_support.c:273: warning: implicit declaration of function `show_xpm'
> > /home/lunn/eCos/anoncvs-clean/packages/hal/sh/dreamcast/current/src/fb_support.c: In function `_hexdigit':
> > /home/lunn/eCos/anoncvs-clean/packages/hal/sh/dreamcast/current/src/fb_support.c:435: warning: control reaches end of non-void function
> > build finished
> >
> > So it builds O.K. for me in the default configuration.
> >
> >   Andrew
> >
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2006-06-18  3:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17  3:50 Gregg Levine
2006-06-17  8:00 ` Andrew Lunn
2006-06-17  8:03   ` Andrew Lunn
2006-06-17 16:09     ` Gregg Levine
2006-06-18  3:24       ` Gregg Levine [this message]

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=18d205ed0606172024y217b51cdk6871fb734e5ed4e3@mail.gmail.com \
    --to=gregg.drwho8@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).