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

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

[servo gmrt]

Dear All,

I am trying to build rtai-4.0-test2 but it fails on my system

I am using buildroot-2014.02 version

When I compile the RTAI-4.0-test2 version I am getting the following error
messages,

>>> rtai 4.0-test2 Building
PATH="/run/media/thiyagu/data/buildroot/output/host/bin:/run/media/thiyagu/data/buildroot/output/host/usr/bin:/run/media/thiyagu/data/buildroot/output/host/usr/sbin/:/usr/lib/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin"
PERLLIB="/run/media/thiyagu/data/buildroot/output/host/usr/lib/perl"
/bin/make -j1  -C
/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/
make[1]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2'
/bin/make  all-recursive
make[2]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2'
Making all in base
make[3]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base'
Making all in include
make[4]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include'
Making all in asm-x86
make[5]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include/asm-x86'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include/asm-x86'
make[5]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include'
make[5]: Nothing to be done for `all-am'.
make[5]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include'
make[4]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/include'
Making all in malloc
make[4]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/malloc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/malloc'
Making all in sched
make[4]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched'
Making all in liblxrt
make[5]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched/liblxrt'
make[5]: Nothing to be done for `all'.
make[5]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched/liblxrt'
make[5]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched'
make[6]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch'
make[7]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal'
/run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
option -- 'E'
Usage:
    ccache [options]
    ccache compiler [compiler options]
    compiler [compiler options]          (via symbolic link)

Options:
    -c, --cleanup         delete old files and recalculate size counters
                          (normally not needed as this is done
automatically)
    -C, --clear           clear the cache completely
    -F, --max-files=N     set maximum number of files in cache to N (use 0
for
                          no limit)
    -M, --max-size=SIZE   set maximum size of cache to SIZE (use 0 for no
                          limit; available suffixes: G, M and K; default
                          suffix: G)
    -s, --show-stats      show statistics summary
    -z, --zero-stats      zero statistics counters

    -h, --help            print this help text
    -V, --version         print version and copyright information

See also <http://ccache.samba.org>.
/run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
option -- 'E'
Usage:
    ccache [options]
    ccache compiler [compiler options]
    compiler [compiler options]          (via symbolic link)

Options:
    -c, --cleanup         delete old files and recalculate size counters
                          (normally not needed as this is done
automatically)
    -C, --clear           clear the cache completely
    -F, --max-files=N     set maximum number of files in cache to N (use 0
for
                          no limit)
    -M, --max-size=SIZE   set maximum size of cache to SIZE (use 0 for no
                          limit; available suffixes: G, M and K; default
                          suffix: G)
    -s, --show-stats      show statistics summary
    -z, --zero-stats      zero statistics counters

    -h, --help            print this help text
    -V, --version         print version and copyright information

See also <http://ccache.samba.org>.
/run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
option -- 'p'
Usage:
    ccache [options]
    ccache compiler [compiler options]
    compiler [compiler options]          (via symbolic link)

Options:
    -c, --cleanup         delete old files and recalculate size counters
                          (normally not needed as this is done
automatically)
    -C, --clear           clear the cache completely
    -F, --max-files=N     set maximum number of files in cache to N (use 0
for
                          no limit)
    -M, --max-size=SIZE   set maximum size of cache to SIZE (use 0 for no
                          limit; available suffixes: G, M and K; default
                          suffix: G)
    -s, --show-stats      show statistics summary
    -z, --zero-stats      zero statistics counters

    -h, --help            print this help text
    -V, --version         print version and copyright information

See also <http://ccache.samba.org>.
make[8]: Entering directory
`/run/media/thiyagu/data/buildroot/output/build/linux-3.8.13'
make[8]: Nothing to be done for
`/run/media/thiyagu/data/buildroot/output/host/usr/bin/i486-buildroot-linux-gnu-gcc'.
  CC [M]
/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal/hal.o
/run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
option -- 'W'
Usage:
    ccache [options]
    ccache compiler [compiler options]
    compiler [compiler options]          (via symbolic link)

Options:
    -c, --cleanup         delete old files and recalculate size counters
                          (normally not needed as this is done
automatically)
    -C, --clear           clear the cache completely
    -F, --max-files=N     set maximum number of files in cache to N (use 0
for
                          no limit)
    -M, --max-size=SIZE   set maximum size of cache to SIZE (use 0 for no
                          limit; available suffixes: G, M and K; default
                          suffix: G)
    -s, --show-stats      show statistics summary
    -z, --zero-stats      zero statistics counters

    -h, --help            print this help text
    -V, --version         print version and copyright information

See also <http://ccache.samba.org>.
make[9]: ***
[/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal/hal.o]
Error 1
make[8]: ***
[_module_/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal]
Error 2
make[8]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/linux-3.8.13'
make[7]: *** [rtai_hal.ko] Error 2
make[7]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal'
make[6]: *** [rtai_hal.ko] Error 2
make[6]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch'
make[5]: *** [rtai_sched.ko] Error 2
make[5]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/sched'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2'
make: ***
[/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/.stamp_built]
Error 2


Please help to resolve the issue.

Thanks & Regards,

B.Thiyagarajan,
GMRT-TIFR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140130/eab00aeb/attachment.html>

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

[Thomas Petazzoni]

Hello,

On Thu, 30 Jan 2014 19:23:38 +0530, servo gmrt wrote:
> Dear All,
> 
> I am trying to build rtai-4.0-test2 but it fails on my system
> 
> I am using buildroot-2014.02 version
> 
> When I compile the RTAI-4.0-test2 version I am getting the following error
> messages,

Please provide the patches you applied to Buildroot in order to build
RTAI 4.0, so that we can reproduce the problem.

> `/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal'
> /run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
> option -- 'E'

This is most likely caused by missing quotes around $(CC) somewhere,
but we would have to reproduce.

> Please help to resolve the issue.

Only if you provide the necessary elements :-)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[servo gmrt]

Dear Thomas,

 Thanks for the replay,

 I am applied rtai-4.0 hal patches to linux source (3.8.13) folder in
output/build/ directory, and i configured rtai-4.0.

 I am attaching the buildroot, linux-3.8.13 and rtai-config files for your
references.




* For your kind informaion i added qiv and xv packages to ,   Target
Packages -----> Graphic libraries and applications*,



Regards,

B.Thiyagarajan


On Fri, Jan 31, 2014 at 12:38 AM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Thu, 30 Jan 2014 19:23:38 +0530, servo gmrt wrote:
> > Dear All,
> >
> > I am trying to build rtai-4.0-test2 but it fails on my system
> >
> > I am using buildroot-2014.02 version
> >
> > When I compile the RTAI-4.0-test2 version I am getting the following
> error
> > messages,
>
> Please provide the patches you applied to Buildroot in order to build
> RTAI 4.0, so that we can reproduce the problem.
>
> >
> `/run/media/thiyagu/data/buildroot/output/build/rtai-4.0-test2/base/arch/x86/hal'
> > /run/media/thiyagu/data/buildroot/output/host/usr/bin/ccache: invalid
> > option -- 'E'
>
> This is most likely caused by missing quotes around $(CC) somewhere,
> but we would have to reproduce.
>
> > Please help to resolve the issue.
>
> Only if you provide the necessary elements :-)
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140131/d8992f8b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot-config
Type: application/octet-stream
Size: 47591 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140131/d8992f8b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-3.8.13-config
Type: application/octet-stream
Size: 66722 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140131/d8992f8b/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtai-4.0-test2-config
Type: application/octet-stream
Size: 1979 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140131/d8992f8b/attachment-0002.obj>

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

[Thomas Petazzoni]

Dear servo gmrt,

On Fri, 31 Jan 2014 10:43:54 +0530, servo gmrt wrote:

>  Thanks for the replay,
> 
>  I am applied rtai-4.0 hal patches to linux source (3.8.13) folder in
> output/build/ directory, and i configured rtai-4.0.
> 
>  I am attaching the buildroot, linux-3.8.13 and rtai-config files for your
> references.

Thanks, but to be able to build RTAI 4.0 altogether, you have certainly
made changes to Buildroot itself. This is the changes I am asking for,
so that I can reproduce your problem.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

[servo gmrt]

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 ?

Thanks & Regards,
B.Thiyagarajan


On Fri, Jan 31, 2014 at 1:34 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Dear servo gmrt,
>
> On Fri, 31 Jan 2014 10:43:54 +0530, servo gmrt wrote:
>
> >  Thanks for the replay,
> >
> >  I am applied rtai-4.0 hal patches to linux source (3.8.13) folder in
> > output/build/ directory, and i configured rtai-4.0.
> >
> >  I am attaching the buildroot, linux-3.8.13 and rtai-config files for
> your
> > references.
>
> Thanks, but to be able to build RTAI 4.0 altogether, you have certainly
> made changes to Buildroot itself. This is the changes I am asking for,
> so that I can reproduce your problem.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140131/a9756709/attachment.html>

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

[Arnout Vandecappelle]

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

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

[servo gmrt]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140208/3f721cd3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtai-diff.patch
Type: text/x-patch
Size: 563 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140208/3f721cd3/attachment.bin>

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

[servo gmrt]

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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140209/d267e407/attachment.html>

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

[Arnout Vandecappelle]

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

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

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

[Arnout Vandecappelle]

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


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