buildroot(busybox) problem with ccache during rtai-4.0-test2 compiling.

Dear Arnout,

     Herewith I am attaching the changes I made in the buildroot, to
compile the rtai-4.0.

    I took the 02-08-2014 daily snapshot from buildroot download repository.

    I used the following command to generate the patch,

      "diff -uprN working-dir original-source-dir"

    Is above command sufficient or do I need to add any flags along with
diff command.


Regards,
B.Thiyagarajan





On Tue, Feb 4, 2014 at 2:38 PM, Arnout Vandecappelle <arnout@mind.be> wrote:

> On 31/01/14 12:09, servo gmrt wrote:
> > I am trying to build integrated linux-kernal, rootfs, and rtai,
> >
> > To complie rtai, I enabled rtai and patch location in .config file. Other
> > than that I have not made any changes in any of the buildroot files.
> >
> > Is there any changes I should make in buoldroot before buliding RTAI ?
>
>  The RTAI version we have in buildroot is RTAI 3.8.1. So if you are
> building RTAI 4.0, it means you are using a fork. So either you have to
> contact the maintainer of your fork, or you have to give us the patches
> that were applied in order to use RTAI 4.0.
>
>  Regards,
>  Arnout
>
> >
> > Thanks & Regards,
> > B.Thiyagarajan
> >
>
>
> --
> Arnout Vandecappelle                          arnout at mind be
> Senior Embedded Software Architect            +32-16-286500
> Essensium/Mind                                http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
>

Dear All,

    I am able to successfully build the linux kernal with RTAI-4.0, While
building i noticed the following,

 1. when we enable the "compiler cache" in Build options I am getting the
above error, after disabling the compiler cache and re-configuring the RTAI
build succeed.

2.  My host system is "i686" but i am building linux for "i486", whenever i
executed the "make linux-menuconfig", buildroot only builds the
linux-kernel modules, it is not building the rtai modules, while testing
the new build system and rtai, kernel reports the "unknown symbols in rtai
modules".

3.  Is there any provision in buildroot, to automatically build the RTAI
modules whenever "make linux-menuconfig" executed ?


Thanks for the buildroot community and supporters helped me to build the
minimal embedded system.


Thanks & Regards,

B.Thiyagarajan
GMRT-SERVO




On Sat, Feb 8, 2014 at 6:49 PM, servo gmrt <servo.gmrt@gmail.com> wrote:

> Dear Arnout,
>
>      Herewith I am attaching the changes I made in the buildroot, to
> compile the rtai-4.0.
>
>     I took the 02-08-2014 daily snapshot from buildroot download
> repository.
>
>     I used the following command to generate the patch,
>
>       "diff -uprN working-dir original-source-dir"
>
>     Is above command sufficient or do I need to add any flags along with
> diff command.
>
>
> Regards,
> B.Thiyagarajan
>
>
>
>
>
> On Tue, Feb 4, 2014 at 2:38 PM, Arnout Vandecappelle <arnout@mind.be>wrote:
>
>> On 31/01/14 12:09, servo gmrt wrote:
>> > I am trying to build integrated linux-kernal, rootfs, and rtai,
>> >
>> > To complie rtai, I enabled rtai and patch location in .config file.
>> Other
>> > than that I have not made any changes in any of the buildroot files.
>> >
>> > Is there any changes I should make in buoldroot before buliding RTAI ?
>>
>>  The RTAI version we have in buildroot is RTAI 3.8.1. So if you are
>> building RTAI 4.0, it means you are using a fork. So either you have to
>> contact the maintainer of your fork, or you have to give us the patches
>> that were applied in order to use RTAI 4.0.
>>
>>  Regards,
>>  Arnout
>>
>> >
>> > Thanks & Regards,
>> > B.Thiyagarajan
>> >
>>
>>
>> --
>> Arnout Vandecappelle                          arnout at mind be
>> Senior Embedded Software Architect            +32-16-286500
>> Essensium/Mind                                http://www.mind.be
>> G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
>> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
>> GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
>>
>
>

On 02/08/14 14:19, servo gmrt wrote:
> Dear Arnout,
> 
>      Herewith I am attaching the changes I made in the buildroot, to
> compile the rtai-4.0.
> 
>     I took the 02-08-2014 daily snapshot from buildroot download repository.
> 
>     I used the following command to generate the patch,
> 
>       "diff -uprN working-dir original-source-dir"
> 
>     Is above command sufficient or do I need to add any flags along with
> diff command.


 So you just bumped the version number to 4.0. Clearly, that is not enough.

 As Thomas mentioned in his first reply: it's a problem with missing
quotes around $(CC) in one of the scripts used by rtai - most likely the
configure script itself. You can try to fix it there. Or you can disable
ccache (and do a 'make rtai-dirclean'), which will probably get you further.

 There is a reasonable chance, however, that you'll encounter other
problems along the way.


 Regards,
 Arnout

On 02/09/14 13:12, servo gmrt wrote:
> 2.  My host system is "i686" but i am building linux for "i486", whenever
> i executed the "make linux-menuconfig", buildroot only builds the
> linux-kernel modules, it is not building the rtai modules, while testing
> the new build system and rtai, kernel reports the "unknown symbols in
> rtai modules".
> 
> 3.  Is there any provision in buildroot, to automatically build the RTAI
> modules whenever "make linux-menuconfig" executed ?

 Since I never used RTAI myself, I'm just guessing here, but I guess the
rtai modules are patched directly into the kernel with the rtai patch. In
that case, it's the kernel's build system that takes care of dependency
tracking. Normally the kernel build system is quite good at getting the
dependencies right, but perhaps the rtai people fumbled it. Note, BTW,
that 'make linux-menuconfig' doesn't rebuild anything, you have to do a
'make' again to actually build.

 If the rtai modules are not patched into the kernel but are built as
part of the rtai package, then you have to do an explicit 'make
rtai-rebuild' after the menuconfig. When you do a partial rebuild,
buildroot doesn't try to guess which packages should be rebuilt as well.
This is intentional, because it would be pretty complex to do, and not
guaranteed to be correct anyway.


 Regards,
 Arnout