This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: [kaffe] Problem of porting kaffe to ecos on ARM 7hardware target
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Dalibor Topic <robilad at kaffe dot org>
- Cc: Danny <D dot Mauersberger at gmx dot net>, kaffe at kaffe dot org,eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 17 Aug 2005 09:50:56 -0600
- Subject: Re: [ECOS] Re: [kaffe] Problem of porting kaffe to ecos on ARM 7hardware target
- References: <E1DwhD6-0003Zi-00@pogo.kaffe.org> <43035A9C.7050607@kaffe.org>
On Wed, 2005-08-17 at 17:41 +0200, Dalibor Topic wrote:
> Danny wrote:
> > Hello list!
> >
> >
>
> Hi Danny,
>
> sorry for the long delay, I just noticed that you had an interesting
> ecos-arm build problem while replying to another mail regarding ecos-arm
> a few moments ago.
>
> > patching file configure
> >
> > Hunk #1 succeeded at 10109 (offset -205 lines).
> >
> > Hunk #2 FAILED at 10629.
> >
> > Hunk #3 FAILED at 10921.
> >
> > Hunk #4 FAILED at 10952.
> >
> > Hunk #5 FAILED at 11029.
> >
> > Hunk #6 FAILED at 11178.
> >
> > Hunk #7 FAILED at 11209.
> >
> > 6 out of 7 hunks FAILED -- saving rejects to file configure.rej patching
> > file configure.in
>
> that's not a big issue, it just indicates that different versions of
> autotools were used in the process of generation of the configure
> script, afaik. You can regenerate the configure script by running bash
> developers/autogen.sh in the top level source directory.
>
> > export KAFFEH=/usr/local/kaffe-1.0.7/kaffe-native/kaffe/kaffeh/kaffeh
> >
> > export LDFLAGS="-L/usr/local/Projekt/Version1/untitled1_install/lib
> > -nostartfiles -Ttarget.ld -WI,--gc-sections"
> >
> > export CFLAGS="-mcpu=arm7tdmi -mbig-endian -Wall -g -O2 -D__ECOS"
> >
> > export CPPFLAGS="-I/usr/local/Projekt/Version1/untitled1_install/include
> > -nostdinc -D__ECOS"
>
> -nostdinc is probably the flag that causes the pain down there in the
> compilation step. It means that the compiler will not look into its own
> include paths.
>
> > When I execute "configure", do I have to add the option "--
> > with-includes", because the first error in make is:
> >
> >
> >
> > "stddef.h: No such file or directory". When I do this, there are
> > still so many errors.
> >
>
> If you need to to that for ecos, then you need to do that :) I don't
> know mysef, as I have not built software for ecos yet. I'd suggest
> removing -nostdinc though.
No, -nostdinc is expected when building for eCos.
I'm guessing that Danny did not start with an eCos configuration which
supports stdio.
Danny - what template did you use for your eCos configuration.
>
> > Do I have to say the compiler, where to find some special header files?
> > Does the compiler takes the wrong header files or does the compiler
> > takes the system header files of my system (Linux) instead of taking the
> > header files both of eCos and kaffe?
>
> the compiler should take its own header files by default (for things
> like sys/...), and then use whatever is specified in its build environment.
>
> cheers,
> dalibor topic
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss