Re: [rtems commit] nfsclient: Avoid __FILE__ and __LINE__

2014-12-05 Thread Gedare Bloom
Should we avoid these macros in general, and say so in coding conventions? On Fri, Dec 5, 2014 at 7:10 AM, Sebastian Huber wrote: > Module:rtems > Branch:master > Commit:b657ea4d33ca47d1bf714906ecc4073c1441c620 > Changeset: > http://git.rtems.org/rtems/commit/?id=b657ea4d33ca47d1bf71

Re: [rtems commit] nfsclient: Avoid __FILE__ and __LINE__

2014-12-05 Thread Sebastian Huber
On 05/12/14 14:49, Gedare Bloom wrote: Should we avoid these macros in general, and say so in coding conventions? Yes, I think we should ban __FILE__, __LINE__ and __DATE__. The only exception should be _Assert(). If we do this, then assert() must be replaced with _Assert(). We should als

RTEMS SMP configuration

2014-12-05 Thread Hesham Moustafa
Hi, Should I add anything other than --enable-smp at configuration line and RTEMS_CHECK_SMP AM_CONDITIONAL(HAS_SMP,[test "$rtems_cv_HAS_SMP" = "yes"]) to bsp configure.ac file to make the building system collects SMP files (e.g, smpimpl.h). I always get undefined reference to some SMP functions li

Re: RTEMS SMP configuration

2014-12-05 Thread Hesham Moustafa
I had to add epiphany to the list RTEMS CPUs that support SMP at aclocal/enable-smp.m4 On Fri, Dec 5, 2014 at 5:06 PM, Hesham Moustafa wrote: > Hi, > > Should I add anything other than --enable-smp at configuration line > and RTEMS_CHECK_SMP > AM_CONDITIONAL(HAS_SMP,[test "$rtems_cv_HAS_SMP" = "y

Freestanding and Hosted implementations.

2014-12-05 Thread Fernando Alberione
Hello, I'm making a research about embbedded OS that are using C++ compilers. Particularly I need to know: 1) Are you using a freestanding or hosted implementation of the C++ library headers? I mean, how do you define the macro __STDC_HOSTED__? 2) What C++ and C library headers are you currently

Re: Freestanding and Hosted implementations.

2014-12-05 Thread Gedare Bloom
Hosted. We use the libstdc++ built with gcc/g++, and for libc we use newlib. I'm not that familiar with limits on the C++ headers. For libc, see [1] which states support for "POSIX 1003.1b-1993, POSIX 1003.1h/D3, and Open Group Single UNIX Specification. Much of the POSIX API standard is actuall

Re: RTEMS SMP configuration

2014-12-05 Thread Hesham Moustafa
It seems like adding an entry for epiphany at aclocal/enable-smp.m4 is not enough, I still get the same error, any hints? On Fri, Dec 5, 2014 at 6:03 PM, Hesham Moustafa wrote: > I had to add epiphany to the list RTEMS CPUs that support SMP at > aclocal/enable-smp.m4 > > On Fri, Dec 5, 2014 at 5:

Re: RTEMS SMP configuration

2014-12-05 Thread Gedare Bloom
Look for where the undefined functions exist and see what guards in the build system or the source code itself might be precluding them from your build. Make sure you re-bootstrap and re-configure a clean build, as old files might cause problems. -Gedare On Fri, Dec 5, 2014 at 3:09 PM, Hesham Mo

Re: RTEMS SMP configuration

2014-12-05 Thread Hesham Moustafa
On Fri, Dec 5, 2014 at 8:36 PM, Gedare Bloom wrote: > Look for where the undefined functions exist and see what guards in > the build system or the source code itself might be precluding them > from your build. > Most of SMP files are guarded with HAS_SMP and RTEMS_SMP. I always run boostrap -p an

Re: RTEMS SMP configuration

2014-12-05 Thread Joel Sherrill
On December 5, 2014 2:40:59 PM CST, Hesham Moustafa wrote: >On Fri, Dec 5, 2014 at 8:36 PM, Gedare Bloom wrote: >> Look for where the undefined functions exist and see what guards in >> the build system or the source code itself might be precluding them >> from your build. >> >Most of SMP file

duplicate functionality in libmd and libcrypt

2014-12-05 Thread Gedare Bloom
Sebastian, Do you intend to phase out libmd? Gedare ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel