[ECOS] GCC 4.3.x problem

[ECOS] GCC 4.3.x problem

[Gary Thomas]

I'm trying to build using GCC 4.3.2 (I build my own, but as
far as I can see, the patch set is the same as the eCosCentric
version).  I get this error:

In file included from /tmp/test/ROMRAM/install/include/dirent.h:64,
                 from /opt/ecos/packages/fs/jffs2/current/src/os-ecos.h:36,
                 from /opt/ecos/packages/fs/jffs2/current/src/nodelist.h:25,
                 from /opt/ecos/packages/fs/jffs2/current/src/fs-ecos.c:16:
/tmp/test/ROMRAM/install/include/limits.h:222:26: error: limits.h: No such file or directory

This stems from <ecos>/packages/isoinfra/current/include/limits.h

/* When using a crosscompiler targeting linux, the next limits.h file
   in the include sequence may be the glibc header - which breaks our
   world. So skip it by defining _LIBC_LIMITS_H_ */
#define _LIBC_LIMITS_H_

/* Secondly only include if we haven't already been included by it. */
#ifndef _GCC_LIMITS_H_
# include_next <limits.h>
#endif

Note: my source tree is a bit old (pre flash-v2 merge), but I can't
see what might have changed that affects this.

Ideas anyone?

-- 
------------------------------------------------------------
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

Re: [ECOS] GCC 4.3.x problem

[Jonathan Larmour]

Gary Thomas wrote:
> I'm trying to build using GCC 4.3.2 (I build my own, but as
> far as I can see, the patch set is the same as the eCosCentric
> version).  I get this error:
> 
> In file included from /tmp/test/ROMRAM/install/include/dirent.h:64,
>                  from /opt/ecos/packages/fs/jffs2/current/src/os-ecos.h:36,
>                  from /opt/ecos/packages/fs/jffs2/current/src/nodelist.h:25,
>                  from /opt/ecos/packages/fs/jffs2/current/src/fs-ecos.c:16:
> /tmp/test/ROMRAM/install/include/limits.h:222:26: error: limits.h: No such file or directory
> 
> This stems from <ecos>/packages/isoinfra/current/include/limits.h
> 
> /* When using a crosscompiler targeting linux, the next limits.h file
>    in the include sequence may be the glibc header - which breaks our
>    world. So skip it by defining _LIBC_LIMITS_H_ */
> #define _LIBC_LIMITS_H_
> 
> /* Secondly only include if we haven't already been included by it. */
> #ifndef _GCC_LIMITS_H_
> # include_next <limits.h>
> #endif
> 
> Note: my source tree is a bit old (pre flash-v2 merge), but I can't
> see what might have changed that affects this.
> 
> Ideas anyone?

Oh yes, we have this fixed. I hadn't thought about it when submitting
toolchain patches. I'll submit it.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

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

Re: [ECOS] GCC 4.3.x problem

[Jonathan Larmour]

Jonathan Larmour wrote:
> Gary Thomas wrote:
>> I'm trying to build using GCC 4.3.2 (I build my own, but as
>> far as I can see, the patch set is the same as the eCosCentric
>> version).  I get this error:
>>
>> In file included from /tmp/test/ROMRAM/install/include/dirent.h:64,
>>                  from /opt/ecos/packages/fs/jffs2/current/src/os-ecos.h:36,
>>                  from /opt/ecos/packages/fs/jffs2/current/src/nodelist.h:25,
>>                  from /opt/ecos/packages/fs/jffs2/current/src/fs-ecos.c:16:
>> /tmp/test/ROMRAM/install/include/limits.h:222:26: error: limits.h: No such file or directory
[snip]
>> Note: my source tree is a bit old (pre flash-v2 merge), but I can't
>> see what might have changed that affects this.
> 
> Oh yes, we have this fixed. I hadn't thought about it when submitting
> toolchain patches. I'll submit it.

Bzzt to me. I did think about it and I did submit it. It came with the
flash v2 merge.

This is the important bit:

Index: cdl/jffs2.cdl
===================================================================
RCS file: /cvs/ecos/ecos/packages/fs/jffs2/current/cdl/jffs2.cdl,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -5 -p -r1.24 -r1.25
--- cdl/jffs2.cdl       1 May 2008 09:35:19 -0000       1.24
+++ cdl/jffs2.cdl       18 Nov 2008 01:28:11 -0000      1.25
@@ -232,11 +232,12 @@ cdl_package CYGPKG_FS_JFFS2 {
        flavor  data
        no_define
        # We add '-D__ECOS' to trigger eCos-specific code in places.
        # We add '-nostdinc -iwithprefix include' to avoid picking up
        #    native <linux/*.h> include files when building on Linux.
-       default_value { "-D__ECOS -nostdinc -iwithprefix include" }
+       default_value { "-D__ECOS " . \
+            (CYGPKG_HAL_SYNTH ? " -nostdinc -iwithprefix include" : "") }
        description   "
            This option modifies the set of compiler flags for
             building the JFFS2 package.
             These flags are used in addition
             to the set of global flags."


Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine

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

Re: [ECOS] GCC 4.3.x problem

[Gary Thomas]

Jonathan Larmour wrote:
> Jonathan Larmour wrote:
>> Gary Thomas wrote:
>>> I'm trying to build using GCC 4.3.2 (I build my own, but as
>>> far as I can see, the patch set is the same as the eCosCentric
>>> version).  I get this error:
>>>
>>> In file included from /tmp/test/ROMRAM/install/include/dirent.h:64,
>>>                  from /opt/ecos/packages/fs/jffs2/current/src/os-ecos.h:36,
>>>                  from /opt/ecos/packages/fs/jffs2/current/src/nodelist.h:25,
>>>                  from /opt/ecos/packages/fs/jffs2/current/src/fs-ecos.c:16:
>>> /tmp/test/ROMRAM/install/include/limits.h:222:26: error: limits.h: No such file or directory
> [snip]
>>> Note: my source tree is a bit old (pre flash-v2 merge), but I can't
>>> see what might have changed that affects this.
>> Oh yes, we have this fixed. I hadn't thought about it when submitting
>> toolchain patches. I'll submit it.
> 
> Bzzt to me. I did think about it and I did submit it. It came with the
> flash v2 merge.
> 
> This is the important bit:
> 
> Index: cdl/jffs2.cdl
> ===================================================================
> RCS file: /cvs/ecos/ecos/packages/fs/jffs2/current/cdl/jffs2.cdl,v
> retrieving revision 1.24
> retrieving revision 1.25
> diff -u -5 -p -r1.24 -r1.25
> --- cdl/jffs2.cdl       1 May 2008 09:35:19 -0000       1.24
> +++ cdl/jffs2.cdl       18 Nov 2008 01:28:11 -0000      1.25
> @@ -232,11 +232,12 @@ cdl_package CYGPKG_FS_JFFS2 {
>         flavor  data
>         no_define
>         # We add '-D__ECOS' to trigger eCos-specific code in places.
>         # We add '-nostdinc -iwithprefix include' to avoid picking up
>         #    native <linux/*.h> include files when building on Linux.
> -       default_value { "-D__ECOS -nostdinc -iwithprefix include" }
> +       default_value { "-D__ECOS " . \
> +            (CYGPKG_HAL_SYNTH ? " -nostdinc -iwithprefix include" : "") }
>         description   "
>             This option modifies the set of compiler flags for
>              building the JFFS2 package.
>              These flags are used in addition
>              to the set of global flags."

Thanks.  I tried looking through the diffs from where my source
tree was based and got quite lost in the morass...

Once the header/copyright stuff is ironed out and the "official"
eCos 3.0 tree is settled, I'll be merging again (as well as bringing
a fair number of contributions back to the public tree).

-- 
------------------------------------------------------------
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

[ECOS] Forthcoming eCos contributions [ was Re: GCC 4.3.x problem ]

[John Dallaway]

Hi Gary

On Fri, 09 Jan 2009 13:08:27 -0700, Gary Thomas wrote:

> Once the header/copyright stuff is ironed out and the "official"
> eCos 3.0 tree is settled, I'll be merging again (as well as bringing
> a fair number of contributions back to the public tree).

Bearing in mind the recent discussions on eCos contributions, I was
wondering what specifically you're intending to contribute and in what
timescale. It's helpful for the wider eCos community to know what's in
the pipeline. Are you able to provide any details at this stage?

John Dallaway

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