All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
@ 2018-03-15  1:46 dhinakar k
  2018-03-15  2:19 ` Liu, Wenlong
  0 siblings, 1 reply; 14+ messages in thread
From: dhinakar k @ 2018-03-15  1:46 UTC (permalink / raw)
  To: fuego

[-- Attachment #1: Type: text/plain, Size: 11584 bytes --]

Hi Liu,

I am very sorry, somehow I missed out seeing your reply.
Thanks for your suggestion.

Since I missed seeing your reply, I managed it by commenting out the build
part in fuego shell script and transferred the pre-compiled binaries to the
desired location.

I downloaded the latest linaro toolchain but it did not fix the issue.
I also installed the arm64 cross toolchain inside the container using the
install shell script but it also did not fix the issue.

Did you find any permanent fix to this issue?

Regards,
Dhinakar

On Thu, Dec 7, 2017 at 3:51 PM, <fuego-request@lists.linuxfoundation.org>
wrote:

> Send Fuego mailing list submissions to
>         fuego@lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.linuxfoundation.org/mailman/listinfo/fuego
> or, via email, send a message with subject or body 'help' to
>         fuego-request@lists.linuxfoundation.org
>
> You can reach the person managing the list at
>         fuego-owner@lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fuego digest..."
>
>
> Today's Topics:
>
>    1. Re: Configure: error: C preprocessor "aarch64-linux-gnu-cpp"
>       fails sanity check (netperf, dbench tests) (Liu, Wenlong)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 Dec 2017 10:21:06 +0000
> From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com>
> To: "dhinakar.k@samsung.com" <dhinakar.k@samsung.com>,
>         "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org
> >
> Cc: "Tim.Bird@sony.com" <Tim.Bird@sony.com>
> Subject: Re: [Fuego] Configure: error: C preprocessor
>         "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
> Message-ID:
>         <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.
> g08.fujitsu.local>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi dhinakar,
>
>
>
> I think we just have the same situation.
>
> About this issue, it seems that symbolic link ?aarch64-linux-gnu-cpp?
> missing for me(don?t know what the cause is yet).
>
> Creating this symbolic link manually can solve this problem temporarily.
>
>
>
> Hope that?s useful to you.
>
>
>
> Best regards
>
> Liu
>
> From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.
> linuxfoundation.org] On Behalf Of Dhinakar Kalyanasundaram
> Sent: Thursday, November 30, 2017 10:34 PM
> To: fuego@lists.linuxfoundation.org
> Cc: Tim.Bird@sony.com
> Subject: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp"
> fails sanity check (netperf, dbench tests)
>
>
> Dear All,
>
>
>
> I am using Fuego v1.2.1 (main branch not 'next'  branch).
>
> While executing 'netperf', 'dbench' test etc. I am getting 'configure:
> error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check ' error.
>
> I have pasted the error log below for reference.
>
> The aarch64 tool chain has been installed inside the container by
> executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> command.
>
> Is there anything else that I need to setup? Please let me know.
>
>
>
> Also I see the below warning in most of the tests log.
>
> ########################### WARNING ###############################
> Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-Test.
> default.1.1/testlog.txt
> -----
>
> Why is it always referring to 'default.1.1' test? Is it for results
> comparison & charting purpose?
>
>
>
> ....
>
> [buildzone] $ /bin/sh -xe /tmp/hudson7334983476305155012.sh
> + export Reboot=false
> + Reboot=false
> + export Rebuild=false
> + Rebuild=false
> + export Target_PreCleanup=true
> + Target_PreCleanup=true
> + export Target_PostCleanup=true
> + Target_PostCleanup=true
> + export TESTDIR=Benchmark.netperf
> + TESTDIR=Benchmark.netperf
> + export TESTSPEC=default
> + TESTSPEC=default
> + timeout --signal=9 6m /bin/bash /fuego-core/engine/scripts/main.sh
> Using nosyslogd.dist overlay
> ##### doing fuego phase: pre_test ########
> Logged in as user root
> Firmware revision: 4.9.0+
>
>
> 01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75
>
>               total        used        free      shared  buff/cache
>  available
> Mem:        2342088       57228     2272632         208       12228
>  2244820
> Swap:             0           0           0
>
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/root       7.2G  4.4G  2.5G  64% /
> devtmpfs        337M     0  337M   0% /dev
> tmpfs           1.2G     0  1.2G   0% /dev/shm
> tmpfs           1.2G   52K  1.2G   1% /tmp
> tmpfs           1.2G  156K  1.2G   1% /run
>
> /dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
> devtmpfs on /dev type devtmpfs (rw,relatime,size=344208k,nr_
> inodes=86052,mode=755)
> proc on /proc type proc (rw,relatime)
> devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
> tmpfs on /tmp type tmpfs (rw,relatime)
> tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> sysfs on /sys type sysfs (rw,relatime)
>
> BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.
>
> Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f
> FILE [FILE]...
>
> Search for PATTERN in FILEs (or stdin)
>
> -H Add 'filename:' prefix
> -h Do not add 'filename:' prefix
> -n Add 'line_no:' prefix
> -l Show only names of files that match
> -L Show only names of files that don't match
> -c Show only count of matching lines
> -o Show only the matching part of line
> -q Quiet. Return 0 if PATTERN is found, 1 otherwise
> -v Select non-matching lines
> -s Suppress open and read errors
> -r Recurse
> -i Ignore case
> -w Match whole words only
> -x Match whole lines only
> -F PATTERN is a literal (not regexp)
> -E PATTERN is an extended regexp
> -m N Match up to N times per file
> -A N Print N lines of trailing context
> -B N Print N lines of leading context
> -C N Same as '-A N -B N'
> -e PTRN Pattern to match
> -f FILE Read pattern from file
>
> [ 5388.605500] sh (2553): drop_caches: 3
>
> ##### doing fuego phase: build ########
>
> Unpacking ../netperf/netperf-2.6.0.tar.bz2
> configure: loading cache config.cache
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... aarch64-unknown-linux-gnu
> checking target system type... aarch64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether aarch64-linux-gnu-gcc accepts -g... yes
> checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of aarch64-linux-gnu-gcc... gcc3
> checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib
> checking for an ANSI C-conforming const... yes
> checking for main in -lm... yes
> checking how to run the C preprocessor... aarch64-linux-gnu-cpp
> configure: error: in `/fuego-rw/buildzone/TRAV-
> Sanity-Test.default.Benchmark.netperf-aarch64':
> configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check
> See `config.log' for more details
> in signal_handler
> Teardown board link
> WARNING: program returned exit code
> Log evaluation may be invalid
> Going to check 1 fail cases for TRAV-Sanity-Test.default.Benchmark.netperf
> grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt:
> No such file or directory
> No fail cases detected for TRAV-Sanity-Test.default.Benchmark.netperf
> running python with PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/
> local/games:/usr/games
> ########################### WARNING ###############################
> Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.
> default.1.1/testlog.txt
> -----
> matches: None
> WARNING: missing or faulty criteria.json file (/fuego-core/engine/tests/
> Benchmark.netperf/criteria.json), looking for reference.log
> converting reference.log for test netperf
> criteria_data= {'schema_version': '1.0', 'criteria': [{'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net'}, {'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_STREAM.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.net'}]}
> No reference.json available
> ref={'test_sets': []}
> Applying criterion {'max_fail': 0, 'tguid': 'Benchmark.netperf'}
> Writing run data to /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.
> default.1.1/run.json
> reference.json not available
> Writing merged results to  /fuego-rw/logs/Benchmark.netperf/results.json
> Writing flat results to /fuego-rw/logs/Benchmark.
> netperf/flat_plot_data.txt
> chart_config.json not available or is wrong format, using default values
> Writing chart data to /fuego-rw/logs/Benchmark.
> netperf/flot_chart_data.json
> ERROR: results did not satisfy the threshold
> Build step 'Execute shell' marked build as failure
> [description-setter] Description set:  <a href="/storm/userContent/
> fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt">testlog</a>
> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/run.json">run.json</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/consolelog.txt">fuegolog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/devlog.txt">devlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/prolog.sh">prolog.sh</a>
> Finished: FAILURE
>
>
>
> Regards,
>
> Dhinakar,
>
> Senior Technical Manager,
>
> 2-07-526, Phoenix Building,
>
> +91-9902007650
>
> Samsung Research Institute, Bangalore.
>
> [cid:image001.png@01D36F84.A9EFAF20]
>
> [Web Bug from http://ext.samsung.net/mail/ext/v1/external/status/update?
> userid=dhinakar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZX
> BjbXM1cDc3NDc0NDljYTkwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcG
> llbnRBZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_]
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d9a1123/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 33527 bytes
> Desc: image001.png
> URL: <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d9a1123/attachment.png>
>
> ------------------------------
>
> _______________________________________________
> Fuego mailing list
> Fuego@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego
>
>
> End of Fuego Digest, Vol 17, Issue 9
> ************************************
>

[-- Attachment #2: Type: text/html, Size: 15850 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-15  1:46 [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests) dhinakar k
@ 2018-03-15  2:19 ` Liu, Wenlong
  2018-03-15  2:46   ` dhinakar k
  0 siblings, 1 reply; 14+ messages in thread
From: Liu, Wenlong @ 2018-03-15  2:19 UTC (permalink / raw)
  To: dhinakar k, fuego

[-- Attachment #1: Type: text/plain, Size: 12599 bytes --]

Hi Dhinakar

> Did you find any permanent fix to this issue?

Sorry, I didn’t use that toolchain any more.
Now, I’m using a yocto toolchain which can help me out.

Thanks.

Best regards
Liu

From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.linuxfoundation.org] On Behalf Of dhinakar k
Sent: Thursday, March 15, 2018 9:46 AM
To: fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)

Hi Liu,
I am very sorry, somehow I missed out seeing your reply.
Thanks for your suggestion.

Since I missed seeing your reply, I managed it by commenting out the build part in fuego shell script and transferred the pre-compiled binaries to the desired location.
I downloaded the latest linaro toolchain but it did not fix the issue.
I also installed the arm64 cross toolchain inside the container using the install shell script but it also did not fix the issue.
Did you find any permanent fix to this issue?
Regards,
Dhinakar

On Thu, Dec 7, 2017 at 3:51 PM, <fuego-request@lists.linuxfoundation.org<mailto:fuego-request@lists.linuxfoundation.org>> wrote:
Send Fuego mailing list submissions to
        fuego@lists.linuxfoundation.org<mailto:fuego@lists.linuxfoundation.org>

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.linuxfoundation.org/mailman/listinfo/fuego
or, via email, send a message with subject or body 'help' to
        fuego-request@lists.linuxfoundation.org<mailto:fuego-request@lists.linuxfoundation.org>

You can reach the person managing the list at
        fuego-owner@lists.linuxfoundation.org<mailto:fuego-owner@lists.linuxfoundation.org>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Fuego digest..."


Today's Topics:

   1. Re: Configure: error: C preprocessor "aarch64-linux-gnu-cpp"
      fails sanity check (netperf, dbench tests) (Liu, Wenlong)


----------------------------------------------------------------------

Message: 1
Date: Thu, 7 Dec 2017 10:21:06 +0000
From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com<mailto:liuwl.fnst@cn.fujitsu.com>>
To: "dhinakar.k@samsung.com<mailto:dhinakar.k@samsung.com>" <dhinakar.k@samsung.com<mailto:dhinakar.k@samsung.com>>,
        "fuego@lists.linuxfoundation.org<mailto:fuego@lists.linuxfoundation.org>" <fuego@lists.linuxfoundation.org<mailto:fuego@lists.linuxfoundation.org>>
Cc: "Tim.Bird@sony.com<mailto:Tim.Bird@sony.com>" <Tim.Bird@sony.com<mailto:Tim.Bird@sony.com>>
Subject: Re: [Fuego] Configure: error: C preprocessor
        "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
Message-ID:
        <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.g08.fujitsu.local<mailto:F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.g08.fujitsu.local>>

Content-Type: text/plain; charset="utf-8"

Hi dhinakar,



I think we just have the same situation.

About this issue, it seems that symbolic link ?aarch64-linux-gnu-cpp? missing for me(don?t know what the cause is yet).

Creating this symbolic link manually can solve this problem temporarily.



Hope that?s useful to you.



Best regards

Liu

From: fuego-bounces@lists.linuxfoundation.org<mailto:fuego-bounces@lists.linuxfoundation.org> [mailto:fuego-bounces@lists.linuxfoundation.org<mailto:fuego-bounces@lists.linuxfoundation.org>] On Behalf Of Dhinakar Kalyanasundaram
Sent: Thursday, November 30, 2017 10:34 PM
To: fuego@lists.linuxfoundation.org<mailto:fuego@lists.linuxfoundation.org>
Cc: Tim.Bird@sony.com<mailto:Tim.Bird@sony.com>
Subject: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)


Dear All,



I am using Fuego v1.2.1 (main branch not 'next'  branch).

While executing 'netperf', 'dbench' test etc. I am getting 'configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check ' error.

I have pasted the error log below for reference.

The aarch64 tool chain has been installed inside the container by executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64' command.

Is there anything else that I need to setup? Please let me know.



Also I see the below warning in most of the tests log.

########################### WARNING ###############################
Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-Test.default.1.1/testlog.txt
-----

Why is it always referring to 'default.1.1' test? Is it for results comparison & charting purpose?



....

[buildzone] $ /bin/sh -xe /tmp/hudson7334983476305155012.sh
+ export Reboot=false
+ Reboot=false
+ export Rebuild=false
+ Rebuild=false
+ export Target_PreCleanup=true
+ Target_PreCleanup=true
+ export Target_PostCleanup=true
+ Target_PostCleanup=true
+ export TESTDIR=Benchmark.netperf
+ TESTDIR=Benchmark.netperf
+ export TESTSPEC=default
+ TESTSPEC=default
+ timeout --signal=9 6m /bin/bash /fuego-core/engine/scripts/main.sh
Using nosyslogd.dist overlay
##### doing fuego phase: pre_test ########
Logged in as user root
Firmware revision: 4.9.0+


01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75

              total        used        free      shared  buff/cache   available
Mem:        2342088       57228     2272632         208       12228     2244820
Swap:             0           0           0

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       7.2G  4.4G  2.5G  64% /
devtmpfs        337M     0  337M   0% /dev
tmpfs           1.2G     0  1.2G   0% /dev/shm
tmpfs           1.2G   52K  1.2G   1% /tmp
tmpfs           1.2G  156K  1.2G   1% /run

/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=344208k,nr_inodes=86052,mode=755)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sysfs on /sys type sysfs (rw,relatime)

BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.

Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

-H Add 'filename:' prefix
-h Do not add 'filename:' prefix
-n Add 'line_no:' prefix
-l Show only names of files that match
-L Show only names of files that don't match
-c Show only count of matching lines
-o Show only the matching part of line
-q Quiet. Return 0 if PATTERN is found, 1 otherwise
-v Select non-matching lines
-s Suppress open and read errors
-r Recurse
-i Ignore case
-w Match whole words only
-x Match whole lines only
-F PATTERN is a literal (not regexp)
-E PATTERN is an extended regexp
-m N Match up to N times per file
-A N Print N lines of trailing context
-B N Print N lines of leading context
-C N Same as '-A N -B N'
-e PTRN Pattern to match
-f FILE Read pattern from file

[ 5388.605500] sh (2553): drop_caches: 3

##### doing fuego phase: build ########

Unpacking ../netperf/netperf-2.6.0.tar.bz2
configure: loading cache config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking target system type... aarch64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether aarch64-linux-gnu-gcc accepts -g... yes
checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of aarch64-linux-gnu-gcc... gcc3
checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib
checking for an ANSI C-conforming const... yes
checking for main in -lm... yes
checking how to run the C preprocessor... aarch64-linux-gnu-cpp
configure: error: in `/fuego-rw/buildzone/TRAV-Sanity-Test.default.Benchmark.netperf-aarch64':
configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check
See `config.log' for more details
in signal_handler
Teardown board link
WARNING: program returned exit code
Log evaluation may be invalid
Going to check 1 fail cases for TRAV-Sanity-Test.default.Benchmark.netperf
grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt: No such file or directory
No fail cases detected for TRAV-Sanity-Test.default.Benchmark.netperf
running python with PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
########################### WARNING ###############################
Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt
-----
matches: None
WARNING: missing or faulty criteria.json file (/fuego-core/engine/tests/Benchmark.netperf/criteria.json), looking for reference.log
converting reference.log for test netperf
criteria_data= {'schema_version': '1.0', 'criteria': [{'reference': {'operator': 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net<http://default.MIGRATED_TCP_MAERTS.net>'}, {'reference': {'operator': 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.cpu'}, {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.net<http://default.MIGRATED_TCP_STREAM.net>'}]}
No reference.json available
ref={'test_sets': []}
Applying criterion {'max_fail': 0, 'tguid': 'Benchmark.netperf'}
Writing run data to /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json
reference.json not available
Writing merged results to  /fuego-rw/logs/Benchmark.netperf/results.json
Writing flat results to /fuego-rw/logs/Benchmark.netperf/flat_plot_data.txt
chart_config.json not available or is wrong format, using default values
Writing chart data to /fuego-rw/logs/Benchmark.netperf/flot_chart_data.json
ERROR: results did not satisfy the threshold
Build step 'Execute shell' marked build as failure
[description-setter] Description set:  <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt">testlog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json">run.json</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/consolelog.txt">fuegolog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/devlog.txt">devlog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/prolog.sh">prolog.sh</a>
Finished: FAILURE



Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

[cid:image001.png@01D36F84.A9EFAF20]

[Web Bug from http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinakar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYTkwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_]


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d9a1123/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 33527 bytes
Desc: image001.png
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d9a1123/attachment.png>

------------------------------

_______________________________________________
Fuego mailing list
Fuego@lists.linuxfoundation.org<mailto:Fuego@lists.linuxfoundation.org>
https://lists.linuxfoundation.org/mailman/listinfo/fuego


End of Fuego Digest, Vol 17, Issue 9
************************************



[-- Attachment #2: Type: text/html, Size: 26915 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-15  2:19 ` Liu, Wenlong
@ 2018-03-15  2:46   ` dhinakar k
  2018-03-20 13:44     ` Tim.Bird
  0 siblings, 1 reply; 14+ messages in thread
From: dhinakar k @ 2018-03-15  2:46 UTC (permalink / raw)
  To: Liu, Wenlong; +Cc: fuego

[-- Attachment #1: Type: text/plain, Size: 12782 bytes --]

Hi Liu,

Thank you very much for your prompt reply.

Anyone else in this forum can help?

Regards,
Dhinakar

On 15 Mar 2018 7:49 am, "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com> wrote:

> Hi Dhinakar
>
>
>
> > Did you find any permanent fix to this issue?
>
>
>
> Sorry, I didn’t use that toolchain any more.
>
> Now, I’m using a yocto toolchain which can help me out.
>
>
>
> Thanks.
>
>
>
> Best regards
>
> Liu
>
>
>
> *From:* fuego-bounces@lists.linuxfoundation.org [mailto:
> fuego-bounces@lists.linuxfoundation.org] *On Behalf Of *dhinakar k
> *Sent:* Thursday, March 15, 2018 9:46 AM
> *To:* fuego@lists.linuxfoundation.org
> *Subject:* Re: [Fuego] Configure: error: C preprocessor
> "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
>
>
>
> Hi Liu,
>
> I am very sorry, somehow I missed out seeing your reply.
>
> Thanks for your suggestion.
>
>
>
> Since I missed seeing your reply, I managed it by commenting out the build
> part in fuego shell script and transferred the pre-compiled binaries to the
> desired location.
>
> I downloaded the latest linaro toolchain but it did not fix the issue.
>
> I also installed the arm64 cross toolchain inside the container using the
> install shell script but it also did not fix the issue.
>
> Did you find any permanent fix to this issue?
>
> Regards,
>
> Dhinakar
>
>
>
> On Thu, Dec 7, 2017 at 3:51 PM, <fuego-request@lists.linuxfoundation.org>
> wrote:
>
> Send Fuego mailing list submissions to
>         fuego@lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.linuxfoundation.org/mailman/listinfo/fuego
> or, via email, send a message with subject or body 'help' to
>         fuego-request@lists.linuxfoundation.org
>
> You can reach the person managing the list at
>         fuego-owner@lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fuego digest..."
>
>
> Today's Topics:
>
>    1. Re: Configure: error: C preprocessor "aarch64-linux-gnu-cpp"
>       fails sanity check (netperf, dbench tests) (Liu, Wenlong)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 7 Dec 2017 10:21:06 +0000
> From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com>
> To: "dhinakar.k@samsung.com" <dhinakar.k@samsung.com>,
>         "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org
> >
> Cc: "Tim.Bird@sony.com" <Tim.Bird@sony.com>
> Subject: Re: [Fuego] Configure: error: C preprocessor
>         "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
> Message-ID:
>         <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.
> g08.fujitsu.local>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi dhinakar,
>
>
>
> I think we just have the same situation.
>
> About this issue, it seems that symbolic link ?aarch64-linux-gnu-cpp?
> missing for me(don?t know what the cause is yet).
>
> Creating this symbolic link manually can solve this problem temporarily.
>
>
>
> Hope that?s useful to you.
>
>
>
> Best regards
>
> Liu
>
> From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.
> linuxfoundation.org] On Behalf Of Dhinakar Kalyanasundaram
> Sent: Thursday, November 30, 2017 10:34 PM
> To: fuego@lists.linuxfoundation.org
> Cc: Tim.Bird@sony.com
> Subject: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp"
> fails sanity check (netperf, dbench tests)
>
>
> Dear All,
>
>
>
> I am using Fuego v1.2.1 (main branch not 'next'  branch).
>
> While executing 'netperf', 'dbench' test etc. I am getting 'configure:
> error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check ' error.
>
> I have pasted the error log below for reference.
>
> The aarch64 tool chain has been installed inside the container by
> executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> command.
>
> Is there anything else that I need to setup? Please let me know.
>
>
>
> Also I see the below warning in most of the tests log.
>
> ########################### WARNING ###############################
> Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-Test.
> default.1.1/testlog.txt
> -----
>
> Why is it always referring to 'default.1.1' test? Is it for results
> comparison & charting purpose?
>
>
>
> ....
>
> [buildzone] $ /bin/sh -xe /tmp/hudson7334983476305155012.sh
> + export Reboot=false
> + Reboot=false
> + export Rebuild=false
> + Rebuild=false
> + export Target_PreCleanup=true
> + Target_PreCleanup=true
> + export Target_PostCleanup=true
> + Target_PostCleanup=true
> + export TESTDIR=Benchmark.netperf
> + TESTDIR=Benchmark.netperf
> + export TESTSPEC=default
> + TESTSPEC=default
> + timeout --signal=9 6m /bin/bash /fuego-core/engine/scripts/main.sh
> Using nosyslogd.dist overlay
> ##### doing fuego phase: pre_test ########
> Logged in as user root
> Firmware revision: 4.9.0+
>
>
> 01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75
>
>               total        used        free      shared  buff/cache
>  available
> Mem:        2342088       57228     2272632         208       12228
>  2244820
> Swap:             0           0           0
>
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/root       7.2G  4.4G  2.5G  64% /
> devtmpfs        337M     0  337M   0% /dev
> tmpfs           1.2G     0  1.2G   0% /dev/shm
> tmpfs           1.2G   52K  1.2G   1% /tmp
> tmpfs           1.2G  156K  1.2G   1% /run
>
> /dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
> devtmpfs on /dev type devtmpfs (rw,relatime,size=344208k,nr_
> inodes=86052,mode=755)
> proc on /proc type proc (rw,relatime)
> devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
> tmpfs on /tmp type tmpfs (rw,relatime)
> tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
> sysfs on /sys type sysfs (rw,relatime)
>
> BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.
>
> Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f
> FILE [FILE]...
>
> Search for PATTERN in FILEs (or stdin)
>
> -H Add 'filename:' prefix
> -h Do not add 'filename:' prefix
> -n Add 'line_no:' prefix
> -l Show only names of files that match
> -L Show only names of files that don't match
> -c Show only count of matching lines
> -o Show only the matching part of line
> -q Quiet. Return 0 if PATTERN is found, 1 otherwise
> -v Select non-matching lines
> -s Suppress open and read errors
> -r Recurse
> -i Ignore case
> -w Match whole words only
> -x Match whole lines only
> -F PATTERN is a literal (not regexp)
> -E PATTERN is an extended regexp
> -m N Match up to N times per file
> -A N Print N lines of trailing context
> -B N Print N lines of leading context
> -C N Same as '-A N -B N'
> -e PTRN Pattern to match
> -f FILE Read pattern from file
>
> [ 5388.605500] sh (2553): drop_caches: 3
>
> ##### doing fuego phase: build ########
>
> Unpacking ../netperf/netperf-2.6.0.tar.bz2
> configure: loading cache config.cache
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... aarch64-unknown-linux-gnu
> checking target system type... aarch64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether aarch64-linux-gnu-gcc accepts -g... yes
> checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of aarch64-linux-gnu-gcc... gcc3
> checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib
> checking for an ANSI C-conforming const... yes
> checking for main in -lm... yes
> checking how to run the C preprocessor... aarch64-linux-gnu-cpp
> configure: error: in `/fuego-rw/buildzone/TRAV-
> Sanity-Test.default.Benchmark.netperf-aarch64':
> configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check
> See `config.log' for more details
> in signal_handler
> Teardown board link
> WARNING: program returned exit code
> Log evaluation may be invalid
> Going to check 1 fail cases for TRAV-Sanity-Test.default.Benchmark.netperf
> grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt:
> No such file or directory
> No fail cases detected for TRAV-Sanity-Test.default.Benchmark.netperf
> running python with PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/
> local/games:/usr/games
> ########################### WARNING ###############################
> Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.
> default.1.1/testlog.txt
> -----
> matches: None
> WARNING: missing or faulty criteria.json file (/fuego-core/engine/tests/
> Benchmark.netperf/criteria.json), looking for reference.log
> converting reference.log for test netperf
> criteria_data= {'schema_version': '1.0', 'criteria': [{'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net'}, {'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_STREAM.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.net'}]}
> No reference.json available
> ref={'test_sets': []}
> Applying criterion {'max_fail': 0, 'tguid': 'Benchmark.netperf'}
> Writing run data to /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.
> default.1.1/run.json
> reference.json not available
> Writing merged results to  /fuego-rw/logs/Benchmark.netperf/results.json
> Writing flat results to /fuego-rw/logs/Benchmark.
> netperf/flat_plot_data.txt
> chart_config.json not available or is wrong format, using default values
> Writing chart data to /fuego-rw/logs/Benchmark.
> netperf/flot_chart_data.json
> ERROR: results did not satisfy the threshold
> Build step 'Execute shell' marked build as failure
> [description-setter] Description set:  <a href="/storm/userContent/
> fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt">testlog</a>
> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/run.json">run.json</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/consolelog.txt">fuegolog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/devlog.txt">devlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/
> TRAV-Sanity-Test.default.1.1/prolog.sh">prolog.sh</a>
> Finished: FAILURE
>
>
>
> Regards,
>
> Dhinakar,
>
> Senior Technical Manager,
>
> 2-07-526, Phoenix Building,
>
> +91-9902007650
>
> Samsung Research Institute, Bangalore.
>
> [cid:image001.png@01D36F84.A9EFAF20]
>
> [Web Bug from http://ext.samsung.net/mail/ext/v1/external/status/update?
> userid=dhinakar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZX
> BjbXM1cDc3NDc0NDljYTkwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcG
> llbnRBZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_]
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d9a1123/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 33527 bytes
> Desc: image001.png
> URL: <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d9a1123/attachment.png>
>
> ------------------------------
>
> _______________________________________________
> Fuego mailing list
> Fuego@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego
>
>
> End of Fuego Digest, Vol 17, Issue 9
> ************************************
>
>

[-- Attachment #2: Type: text/html, Size: 20876 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-15  2:46   ` dhinakar k
@ 2018-03-20 13:44     ` Tim.Bird
  2018-03-22 13:59       ` dhinakar k
       [not found]       ` <CABehs3NKZkvc4nQ8qoR2+cF-HH94zS=67vLXjqCaeFr5urPOAA@mail.gmail.com>
  0 siblings, 2 replies; 14+ messages in thread
From: Tim.Bird @ 2018-03-20 13:44 UTC (permalink / raw)
  To: dhinakar.k, liuwl.fnst; +Cc: fuego



> -----Original Message-----
> From: dhinakar k
> Thank you very much for your prompt reply.
> 
> Anyone else in this forum can help?

I seem to recall working on this problem last year, but I don't recall the details.
Guilherme Camargo just added a patch to use cross-toolchains from
Debian unstable rather than from the Emdebian project.

You might want to check out the latest fuego master repository
and try the 'fuego-ro/toolchains/install_cross_toolchain.sh arm64'
(inside the docker container), and see what happens when building
those tests.

Let me know if this helps.
 -- Tim
 
> Regards,
> Dhinakar
> 
> On 15 Mar 2018 7:49 am, "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> <mailto:liuwl.fnst@cn.fujitsu.com> > wrote:
> 
> 
> 	Hi Dhinakar
> 
> 
> 
> 	> Did you find any permanent fix to this issue?
> 
> 
> 
> 	Sorry, I didn’t use that toolchain any more.
> 
> 	Now, I’m using a yocto toolchain which can help me out.
> 
> 
> 
> 	Thanks.
> 
> 
> 
> 	Best regards
> 
> 	Liu
> 
> 
> 
> 	From: fuego-bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org>  [mailto:fuego-
> bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org> ] On Behalf Of dhinakar k
> 	Sent: Thursday, March 15, 2018 9:46 AM
> 	To: fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
> 	Subject: Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-
> gnu-cpp" fails sanity check (netperf, dbench tests)
> 
> 
> 
> 	Hi Liu,
> 
> 	I am very sorry, somehow I missed out seeing your reply.
> 
> 	Thanks for your suggestion.
> 
> 
> 
> 	Since I missed seeing your reply, I managed it by commenting out the
> build part in fuego shell script and transferred the pre-compiled binaries to
> the desired location.
> 
> 	I downloaded the latest linaro toolchain but it did not fix the issue.
> 
> 	I also installed the arm64 cross toolchain inside the container using
> the install shell script but it also did not fix the issue.
> 
> 	Did you find any permanent fix to this issue?
> 
> 	Regards,
> 
> 	Dhinakar
> 
> 
> 
> 	On Thu, Dec 7, 2017 at 3:51 PM, <fuego-
> request@lists.linuxfoundation.org <mailto:fuego-
> request@lists.linuxfoundation.org> > wrote:
> 
> 		Send Fuego mailing list submissions to
> 		        fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
> 
> 		To subscribe or unsubscribe via the World Wide Web, visit
> 		        https://lists.linuxfoundation.org/mailman/listinfo/fuego
> <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
> 		or, via email, send a message with subject or body 'help' to
> 		        fuego-request@lists.linuxfoundation.org <mailto:fuego-
> request@lists.linuxfoundation.org>
> 
> 		You can reach the person managing the list at
> 		        fuego-owner@lists.linuxfoundation.org <mailto:fuego-
> owner@lists.linuxfoundation.org>
> 
> 		When replying, please edit your Subject line so it is more
> specific
> 		than "Re: Contents of Fuego digest..."
> 
> 
> 		Today's Topics:
> 
> 		   1. Re: Configure: error: C preprocessor "aarch64-linux-gnu-
> cpp"
> 		      fails sanity check (netperf, dbench tests) (Liu, Wenlong)
> 
> 
> 		----------------------------------------------------------------------
> 
> 		Message: 1
> 		Date: Thu, 7 Dec 2017 10:21:06 +0000
> 		From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> <mailto:liuwl.fnst@cn.fujitsu.com> >
> 		To: "dhinakar.k@samsung.com
> <mailto:dhinakar.k@samsung.com> " <dhinakar.k@samsung.com
> <mailto:dhinakar.k@samsung.com> >,
> 		        "fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org> "
> <fuego@lists.linuxfoundation.org <mailto:fuego@lists.linuxfoundation.org>
> >
> 		Cc: "Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> "
> <Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> >
> 		Subject: Re: [Fuego] Configure: error: C preprocessor
> 		        "aarch64-linux-gnu-cpp" fails sanity check (netperf,
> dbench tests)
> 		Message-ID:
> 
> <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.g
> 08.fujitsu.local
> <mailto:F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPE
> KD01.g08.fujitsu.local> >
> 
> 		Content-Type: text/plain; charset="utf-8"
> 
> 		Hi dhinakar,
> 
> 
> 
> 		I think we just have the same situation.
> 
> 		About this issue, it seems that symbolic link ?aarch64-linux-
> gnu-cpp? missing for me(don?t know what the cause is yet).
> 
> 		Creating this symbolic link manually can solve this problem
> temporarily.
> 
> 
> 
> 		Hope that?s useful to you.
> 
> 
> 
> 		Best regards
> 
> 		Liu
> 
> 		From: fuego-bounces@lists.linuxfoundation.org
> <mailto:fuego-bounces@lists.linuxfoundation.org>  [mailto:fuego-
> bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org> ] On Behalf Of Dhinakar
> Kalyanasundaram
> 		Sent: Thursday, November 30, 2017 10:34 PM
> 		To: fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
> 		Cc: Tim.Bird@sony.com <mailto:Tim.Bird@sony.com>
> 		Subject: [Fuego] Configure: error: C preprocessor "aarch64-
> linux-gnu-cpp" fails sanity check (netperf, dbench tests)
> 
> 
> 		Dear All,
> 
> 
> 
> 		I am using Fuego v1.2.1 (main branch not 'next'  branch).
> 
> 		While executing 'netperf', 'dbench' test etc. I am getting
> 'configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check '
> error.
> 
> 		I have pasted the error log below for reference.
> 
> 		The aarch64 tool chain has been installed inside the container
> by executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> command.
> 
> 		Is there anything else that I need to setup? Please let me
> know.
> 
> 
> 
> 		Also I see the below warning in most of the tests log.
> 
> 		########################### WARNING
> ###############################
> 		Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-
> Test.default.1.1/testlog.txt
> 		-----
> 
> 		Why is it always referring to 'default.1.1' test? Is it for results
> comparison & charting purpose?
> 
> 
> 
> 		....
> 
> 		[buildzone] $ /bin/sh -xe
> /tmp/hudson7334983476305155012.sh
> 		+ export Reboot=false
> 		+ Reboot=false
> 		+ export Rebuild=false
> 		+ Rebuild=false
> 		+ export Target_PreCleanup=true
> 		+ Target_PreCleanup=true
> 		+ export Target_PostCleanup=true
> 		+ Target_PostCleanup=true
> 		+ export TESTDIR=Benchmark.netperf
> 		+ TESTDIR=Benchmark.netperf
> 		+ export TESTSPEC=default
> 		+ TESTSPEC=default
> 		+ timeout --signal=9 6m /bin/bash /fuego-
> core/engine/scripts/main.sh
> 		Using nosyslogd.dist overlay
> 		##### doing fuego phase: pre_test ########
> 		Logged in as user root
> 		Firmware revision: 4.9.0+
> 
> 
> 		01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75
> 
> 		              total        used        free      shared  buff/cache   available
> 		Mem:        2342088       57228     2272632         208       12228
> 2244820
> 		Swap:             0           0           0
> 
> 		Filesystem      Size  Used Avail Use% Mounted on
> 		/dev/root       7.2G  4.4G  2.5G  64% /
> 		devtmpfs        337M     0  337M   0% /dev
> 		tmpfs           1.2G     0  1.2G   0% /dev/shm
> 		tmpfs           1.2G   52K  1.2G   1% /tmp
> 		tmpfs           1.2G  156K  1.2G   1% /run
> 
> 		/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
> 		devtmpfs on /dev type devtmpfs
> (rw,relatime,size=344208k,nr_inodes=86052,mode=755)
> 		proc on /proc type proc (rw,relatime)
> 		devpts on /dev/pts type devpts
> (rw,relatime,gid=5,mode=620,ptmxmode=000)
> 		tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
> 		tmpfs on /tmp type tmpfs (rw,relatime)
> 		tmpfs on /run type tmpfs
> (rw,nosuid,nodev,relatime,mode=755)
> 		sysfs on /sys type sysfs (rw,relatime)
> 
> 		BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.
> 
> 		Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-
> e PATTERN.../-f FILE [FILE]...
> 
> 		Search for PATTERN in FILEs (or stdin)
> 
> 		-H Add 'filename:' prefix
> 		-h Do not add 'filename:' prefix
> 		-n Add 'line_no:' prefix
> 		-l Show only names of files that match
> 		-L Show only names of files that don't match
> 		-c Show only count of matching lines
> 		-o Show only the matching part of line
> 		-q Quiet. Return 0 if PATTERN is found, 1 otherwise
> 		-v Select non-matching lines
> 		-s Suppress open and read errors
> 		-r Recurse
> 		-i Ignore case
> 		-w Match whole words only
> 		-x Match whole lines only
> 		-F PATTERN is a literal (not regexp)
> 		-E PATTERN is an extended regexp
> 		-m N Match up to N times per file
> 		-A N Print N lines of trailing context
> 		-B N Print N lines of leading context
> 		-C N Same as '-A N -B N'
> 		-e PTRN Pattern to match
> 		-f FILE Read pattern from file
> 
> 		[ 5388.605500] sh (2553): drop_caches: 3
> 
> 		##### doing fuego phase: build ########
> 
> 		Unpacking ../netperf/netperf-2.6.0.tar.bz2
> 		configure: loading cache config.cache
> 		checking build system type... x86_64-unknown-linux-gnu
> 		checking host system type... aarch64-unknown-linux-gnu
> 		checking target system type... aarch64-unknown-linux-gnu
> 		checking for a BSD-compatible install... /usr/bin/install -c
> 		checking whether build environment is sane... yes
> 		checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
> 		checking for a thread-safe mkdir -p... /bin/mkdir -p
> 		checking for gawk... no
> 		checking for mawk... mawk
> 		checking whether make sets $(MAKE)... yes
> 		checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
> 		checking whether the C compiler works... yes
> 		checking for C compiler default output file name... a.out
> 		checking for suffix of executables...
> 		checking whether we are cross compiling... yes
> 		checking for suffix of object files... o
> 		checking whether we are using the GNU C compiler... yes
> 		checking whether aarch64-linux-gnu-gcc accepts -g... yes
> 		checking for aarch64-linux-gnu-gcc option to accept ISO C89...
> none needed
> 		checking for style of include used by make... GNU
> 		checking dependency style of aarch64-linux-gnu-gcc... gcc3
> 		checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-
> ranlib
> 		checking for an ANSI C-conforming const... yes
> 		checking for main in -lm... yes
> 		checking how to run the C preprocessor... aarch64-linux-gnu-
> cpp
> 		configure: error: in `/fuego-rw/buildzone/TRAV-Sanity-
> Test.default.Benchmark.netperf-aarch64':
> 		configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails
> sanity check
> 		See `config.log' for more details
> 		in signal_handler
> 		Teardown board link
> 		WARNING: program returned exit code
> 		Log evaluation may be invalid
> 		Going to check 1 fail cases for TRAV-Sanity-
> Test.default.Benchmark.netperf
> 		grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt: No such file or directory
> 		No fail cases detected for TRAV-Sanity-
> Test.default.Benchmark.netperf
> 		running python with
> PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gam
> es
> 		########################### WARNING
> ###############################
> 		Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt
> 		-----
> 		matches: None
> 		WARNING: missing or faulty criteria.json file (/fuego-
> core/engine/tests/Benchmark.netperf/criteria.json), looking for
> reference.log
> 		converting reference.log for test netperf
> 		criteria_data= {'schema_version': '1.0', 'criteria': [{'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net
> <http://default.MIGRATED_TCP_MAERTS.net> '}, {'reference': {'operator':
> 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.cpu'},
> {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid':
> 'default.MIGRATED_TCP_STREAM.net
> <http://default.MIGRATED_TCP_STREAM.net> '}]}
> 		No reference.json available
> 		ref={'test_sets': []}
> 		Applying criterion {'max_fail': 0, 'tguid': 'Benchmark.netperf'}
> 		Writing run data to /fuego-
> rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json
> 		reference.json not available
> 		Writing merged results to  /fuego-
> rw/logs/Benchmark.netperf/results.json
> 		Writing flat results to /fuego-
> rw/logs/Benchmark.netperf/flat_plot_data.txt
> 		chart_config.json not available or is wrong format, using
> default values
> 		Writing chart data to /fuego-
> rw/logs/Benchmark.netperf/flot_chart_data.json
> 		ERROR: results did not satisfy the threshold
> 		Build step 'Execute shell' marked build as failure
> 		[description-setter] Description set:  <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt">testlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/run.json">run.json</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/consolelog.txt">fuegolog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/devlog.txt">devlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/prolog.sh">prolog.sh</a>
> 		Finished: FAILURE
> 
> 
> 
> 		Regards,
> 
> 		Dhinakar,
> 
> 		Senior Technical Manager,
> 
> 		2-07-526, Phoenix Building,
> 
> 		+91-9902007650
> 
> 		Samsung Research Institute, Bangalore.
> 
> 		[cid:image001.png@01D36F84.A9EFAF20]
> 
> 		[Web Bug from
> http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinak
> ar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYTk
> wMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPWZ
> 1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYT
> kwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPW
> Z1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_> ]
> 
> 
> 		-------------- next part --------------
> 		An HTML attachment was scrubbed...
> 		URL:
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.html
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.html> >
> 		-------------- next part --------------
> 		A non-text attachment was scrubbed...
> 		Name: image001.png
> 		Type: image/png
> 		Size: 33527 bytes
> 		Desc: image001.png
> 		URL:
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.png
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.png> >
> 
> 		------------------------------
> 
> 
> 	_______________________________________________
> 		Fuego mailing list
> 		Fuego@lists.linuxfoundation.org
> <mailto:Fuego@lists.linuxfoundation.org>
> 		https://lists.linuxfoundation.org/mailman/listinfo/fuego
> <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
> 
> 
> 		End of Fuego Digest, Vol 17, Issue 9
> 		************************************


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-20 13:44     ` Tim.Bird
@ 2018-03-22 13:59       ` dhinakar k
       [not found]       ` <CABehs3NKZkvc4nQ8qoR2+cF-HH94zS=67vLXjqCaeFr5urPOAA@mail.gmail.com>
  1 sibling, 0 replies; 14+ messages in thread
From: dhinakar k @ 2018-03-22 13:59 UTC (permalink / raw)
  To: Tim.Bird; +Cc: fuego

[-- Attachment #1: Type: text/plain, Size: 19103 bytes --]

Thanks a lot Tim, Iam checking them out on a different PC as I don't want
to disturb the current setup. I will keep you and this forum posted on the
results.

Regards,
Dhinakar

On 20 Mar 2018 7:15 pm, <Tim.Bird@sony.com> wrote:

>
>
> > -----Original Message-----
> > From: dhinakar k
> > Thank you very much for your prompt reply.
> >
> > Anyone else in this forum can help?
>
> I seem to recall working on this problem last year, but I don't recall the
> details.
> Guilherme Camargo just added a patch to use cross-toolchains from
> Debian unstable rather than from the Emdebian project.
>
> You might want to check out the latest fuego master repository
> and try the 'fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> (inside the docker container), and see what happens when building
> those tests.
>
> Let me know if this helps.
>  -- Tim
>
> > Regards,
> > Dhinakar
> >
> > On 15 Mar 2018 7:49 am, "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> > <mailto:liuwl.fnst@cn.fujitsu.com> > wrote:
> >
> >
> >       Hi Dhinakar
> >
> >
> >
> >       > Did you find any permanent fix to this issue?
> >
> >
> >
> >       Sorry, I didn’t use that toolchain any more.
> >
> >       Now, I’m using a yocto toolchain which can help me out.
> >
> >
> >
> >       Thanks.
> >
> >
> >
> >       Best regards
> >
> >       Liu
> >
> >
> >
> >       From: fuego-bounces@lists.linuxfoundation.org <mailto:fuego-
> > bounces@lists.linuxfoundation.org>  [mailto:fuego-
> > bounces@lists.linuxfoundation.org <mailto:fuego-
> > bounces@lists.linuxfoundation.org> ] On Behalf Of dhinakar k
> >       Sent: Thursday, March 15, 2018 9:46 AM
> >       To: fuego@lists.linuxfoundation.org
> > <mailto:fuego@lists.linuxfoundation.org>
> >       Subject: Re: [Fuego] Configure: error: C preprocessor
> "aarch64-linux-
> > gnu-cpp" fails sanity check (netperf, dbench tests)
> >
> >
> >
> >       Hi Liu,
> >
> >       I am very sorry, somehow I missed out seeing your reply.
> >
> >       Thanks for your suggestion.
> >
> >
> >
> >       Since I missed seeing your reply, I managed it by commenting out
> the
> > build part in fuego shell script and transferred the pre-compiled
> binaries to
> > the desired location.
> >
> >       I downloaded the latest linaro toolchain but it did not fix the
> issue.
> >
> >       I also installed the arm64 cross toolchain inside the container
> using
> > the install shell script but it also did not fix the issue.
> >
> >       Did you find any permanent fix to this issue?
> >
> >       Regards,
> >
> >       Dhinakar
> >
> >
> >
> >       On Thu, Dec 7, 2017 at 3:51 PM, <fuego-
> > request@lists.linuxfoundation.org <mailto:fuego-
> > request@lists.linuxfoundation.org> > wrote:
> >
> >               Send Fuego mailing list submissions to
> >                       fuego@lists.linuxfoundation.org
> > <mailto:fuego@lists.linuxfoundation.org>
> >
> >               To subscribe or unsubscribe via the World Wide Web, visit
> >                       https://lists.linuxfoundation.
> org/mailman/listinfo/fuego
> > <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
> >               or, via email, send a message with subject or body 'help'
> to
> >                       fuego-request@lists.linuxfoundation.org <mailto:
> fuego-
> > request@lists.linuxfoundation.org>
> >
> >               You can reach the person managing the list at
> >                       fuego-owner@lists.linuxfoundation.org <mailto:
> fuego-
> > owner@lists.linuxfoundation.org>
> >
> >               When replying, please edit your Subject line so it is more
> > specific
> >               than "Re: Contents of Fuego digest..."
> >
> >
> >               Today's Topics:
> >
> >                  1. Re: Configure: error: C preprocessor
> "aarch64-linux-gnu-
> > cpp"
> >                     fails sanity check (netperf, dbench tests) (Liu,
> Wenlong)
> >
> >
> >               ------------------------------
> ----------------------------------------
> >
> >               Message: 1
> >               Date: Thu, 7 Dec 2017 10:21:06 +0000
> >               From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> > <mailto:liuwl.fnst@cn.fujitsu.com> >
> >               To: "dhinakar.k@samsung.com
> > <mailto:dhinakar.k@samsung.com> " <dhinakar.k@samsung.com
> > <mailto:dhinakar.k@samsung.com> >,
> >                       "fuego@lists.linuxfoundation.org
> > <mailto:fuego@lists.linuxfoundation.org> "
> > <fuego@lists.linuxfoundation.org <mailto:fuego@lists.linuxfoundation.org
> >
> > >
> >               Cc: "Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> "
> > <Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> >
> >               Subject: Re: [Fuego] Configure: error: C preprocessor
> >                       "aarch64-linux-gnu-cpp" fails sanity check
> (netperf,
> > dbench tests)
> >               Message-ID:
> >
> > <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.g
> > 08.fujitsu.local
> > <mailto:F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPE
> > KD01.g08.fujitsu.local> >
> >
> >               Content-Type: text/plain; charset="utf-8"
> >
> >               Hi dhinakar,
> >
> >
> >
> >               I think we just have the same situation.
> >
> >               About this issue, it seems that symbolic link
> ?aarch64-linux-
> > gnu-cpp? missing for me(don?t know what the cause is yet).
> >
> >               Creating this symbolic link manually can solve this problem
> > temporarily.
> >
> >
> >
> >               Hope that?s useful to you.
> >
> >
> >
> >               Best regards
> >
> >               Liu
> >
> >               From: fuego-bounces@lists.linuxfoundation.org
> > <mailto:fuego-bounces@lists.linuxfoundation.org>  [mailto:fuego-
> > bounces@lists.linuxfoundation.org <mailto:fuego-
> > bounces@lists.linuxfoundation.org> ] On Behalf Of Dhinakar
> > Kalyanasundaram
> >               Sent: Thursday, November 30, 2017 10:34 PM
> >               To: fuego@lists.linuxfoundation.org
> > <mailto:fuego@lists.linuxfoundation.org>
> >               Cc: Tim.Bird@sony.com <mailto:Tim.Bird@sony.com>
> >               Subject: [Fuego] Configure: error: C preprocessor "aarch64-
> > linux-gnu-cpp" fails sanity check (netperf, dbench tests)
> >
> >
> >               Dear All,
> >
> >
> >
> >               I am using Fuego v1.2.1 (main branch not 'next'  branch).
> >
> >               While executing 'netperf', 'dbench' test etc. I am getting
> > 'configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity
> check '
> > error.
> >
> >               I have pasted the error log below for reference.
> >
> >               The aarch64 tool chain has been installed inside the
> container
> > by executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> > command.
> >
> >               Is there anything else that I need to setup? Please let me
> > know.
> >
> >
> >
> >               Also I see the below warning in most of the tests log.
> >
> >               ########################### WARNING
> > ###############################
> >               Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-
> > Test.default.1.1/testlog.txt
> >               -----
> >
> >               Why is it always referring to 'default.1.1' test? Is it
> for results
> > comparison & charting purpose?
> >
> >
> >
> >               ....
> >
> >               [buildzone] $ /bin/sh -xe
> > /tmp/hudson7334983476305155012.sh
> >               + export Reboot=false
> >               + Reboot=false
> >               + export Rebuild=false
> >               + Rebuild=false
> >               + export Target_PreCleanup=true
> >               + Target_PreCleanup=true
> >               + export Target_PostCleanup=true
> >               + Target_PostCleanup=true
> >               + export TESTDIR=Benchmark.netperf
> >               + TESTDIR=Benchmark.netperf
> >               + export TESTSPEC=default
> >               + TESTSPEC=default
> >               + timeout --signal=9 6m /bin/bash /fuego-
> > core/engine/scripts/main.sh
> >               Using nosyslogd.dist overlay
> >               ##### doing fuego phase: pre_test ########
> >               Logged in as user root
> >               Firmware revision: 4.9.0+
> >
> >
> >               01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75
> >
> >                             total        used        free      shared
> buff/cache   available
> >               Mem:        2342088       57228     2272632         208
>    12228
> > 2244820
> >               Swap:             0           0           0
> >
> >               Filesystem      Size  Used Avail Use% Mounted on
> >               /dev/root       7.2G  4.4G  2.5G  64% /
> >               devtmpfs        337M     0  337M   0% /dev
> >               tmpfs           1.2G     0  1.2G   0% /dev/shm
> >               tmpfs           1.2G   52K  1.2G   1% /tmp
> >               tmpfs           1.2G  156K  1.2G   1% /run
> >
> >               /dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
> >               devtmpfs on /dev type devtmpfs
> > (rw,relatime,size=344208k,nr_inodes=86052,mode=755)
> >               proc on /proc type proc (rw,relatime)
> >               devpts on /dev/pts type devpts
> > (rw,relatime,gid=5,mode=620,ptmxmode=000)
> >               tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
> >               tmpfs on /tmp type tmpfs (rw,relatime)
> >               tmpfs on /run type tmpfs
> > (rw,nosuid,nodev,relatime,mode=755)
> >               sysfs on /sys type sysfs (rw,relatime)
> >
> >               BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call
> binary.
> >
> >               Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-
> > e PATTERN.../-f FILE [FILE]...
> >
> >               Search for PATTERN in FILEs (or stdin)
> >
> >               -H Add 'filename:' prefix
> >               -h Do not add 'filename:' prefix
> >               -n Add 'line_no:' prefix
> >               -l Show only names of files that match
> >               -L Show only names of files that don't match
> >               -c Show only count of matching lines
> >               -o Show only the matching part of line
> >               -q Quiet. Return 0 if PATTERN is found, 1 otherwise
> >               -v Select non-matching lines
> >               -s Suppress open and read errors
> >               -r Recurse
> >               -i Ignore case
> >               -w Match whole words only
> >               -x Match whole lines only
> >               -F PATTERN is a literal (not regexp)
> >               -E PATTERN is an extended regexp
> >               -m N Match up to N times per file
> >               -A N Print N lines of trailing context
> >               -B N Print N lines of leading context
> >               -C N Same as '-A N -B N'
> >               -e PTRN Pattern to match
> >               -f FILE Read pattern from file
> >
> >               [ 5388.605500] sh (2553): drop_caches: 3
> >
> >               ##### doing fuego phase: build ########
> >
> >               Unpacking ../netperf/netperf-2.6.0.tar.bz2
> >               configure: loading cache config.cache
> >               checking build system type... x86_64-unknown-linux-gnu
> >               checking host system type... aarch64-unknown-linux-gnu
> >               checking target system type... aarch64-unknown-linux-gnu
> >               checking for a BSD-compatible install... /usr/bin/install
> -c
> >               checking whether build environment is sane... yes
> >               checking for aarch64-linux-gnu-strip...
> aarch64-linux-gnu-strip
> >               checking for a thread-safe mkdir -p... /bin/mkdir -p
> >               checking for gawk... no
> >               checking for mawk... mawk
> >               checking whether make sets $(MAKE)... yes
> >               checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
> >               checking whether the C compiler works... yes
> >               checking for C compiler default output file name... a.out
> >               checking for suffix of executables...
> >               checking whether we are cross compiling... yes
> >               checking for suffix of object files... o
> >               checking whether we are using the GNU C compiler... yes
> >               checking whether aarch64-linux-gnu-gcc accepts -g... yes
> >               checking for aarch64-linux-gnu-gcc option to accept ISO
> C89...
> > none needed
> >               checking for style of include used by make... GNU
> >               checking dependency style of aarch64-linux-gnu-gcc... gcc3
> >               checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-
> > ranlib
> >               checking for an ANSI C-conforming const... yes
> >               checking for main in -lm... yes
> >               checking how to run the C preprocessor...
> aarch64-linux-gnu-
> > cpp
> >               configure: error: in `/fuego-rw/buildzone/TRAV-Sanity-
> > Test.default.Benchmark.netperf-aarch64':
> >               configure: error: C preprocessor "aarch64-linux-gnu-cpp"
> fails
> > sanity check
> >               See `config.log' for more details
> >               in signal_handler
> >               Teardown board link
> >               WARNING: program returned exit code
> >               Log evaluation may be invalid
> >               Going to check 1 fail cases for TRAV-Sanity-
> > Test.default.Benchmark.netperf
> >               grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/testlog.txt: No such file or directory
> >               No fail cases detected for TRAV-Sanity-
> > Test.default.Benchmark.netperf
> >               running python with
> > PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/
> local/games:/usr/gam
> > es
> >               ########################### WARNING
> > ###############################
> >               Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/testlog.txt
> >               -----
> >               matches: None
> >               WARNING: missing or faulty criteria.json file (/fuego-
> > core/engine/tests/Benchmark.netperf/criteria.json), looking for
> > reference.log
> >               converting reference.log for test netperf
> >               criteria_data= {'schema_version': '1.0', 'criteria':
> [{'reference':
> > {'operator': 'le', 'value': 10000000.0}, 'tguid':
> > 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge',
> > 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net
> > <http://default.MIGRATED_TCP_MAERTS.net> '}, {'reference': {'operator':
> > 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.cpu'},
> > {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid':
> > 'default.MIGRATED_TCP_STREAM.net
> > <http://default.MIGRATED_TCP_STREAM.net> '}]}
> >               No reference.json available
> >               ref={'test_sets': []}
> >               Applying criterion {'max_fail': 0, 'tguid':
> 'Benchmark.netperf'}
> >               Writing run data to /fuego-
> > rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json
> >               reference.json not available
> >               Writing merged results to  /fuego-
> > rw/logs/Benchmark.netperf/results.json
> >               Writing flat results to /fuego-
> > rw/logs/Benchmark.netperf/flat_plot_data.txt
> >               chart_config.json not available or is wrong format, using
> > default values
> >               Writing chart data to /fuego-
> > rw/logs/Benchmark.netperf/flot_chart_data.json
> >               ERROR: results did not satisfy the threshold
> >               Build step 'Execute shell' marked build as failure
> >               [description-setter] Description set:  <a
> > href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/testlog.txt">testlog</a> <a
> > href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/run.json">run.json</a> <a
> > href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/consolelog.txt">fuegolog</a> <a
> > href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/devlog.txt">devlog</a> <a
> > href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> > Test.default.1.1/prolog.sh">prolog.sh</a>
> >               Finished: FAILURE
> >
> >
> >
> >               Regards,
> >
> >               Dhinakar,
> >
> >               Senior Technical Manager,
> >
> >               2-07-526, Phoenix Building,
> >
> >               +91-9902007650
> >
> >               Samsung Research Institute, Bangalore.
> >
> >               [cid:image001.png@01D36F84.A9EFAF20]
> >
> >               [Web Bug from
> > http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinak
> > ar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYTk
> > wMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPWZ
> > 1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_
> > <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> > kar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYT
> > kwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPW
> > Z1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_> ]
> >
> >
> >               -------------- next part --------------
> >               An HTML attachment was scrubbed...
> >               URL:
> > <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d
> > 9a1123/attachment.html
> > <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d
> > 9a1123/attachment.html> >
> >               -------------- next part --------------
> >               A non-text attachment was scrubbed...
> >               Name: image001.png
> >               Type: image/png
> >               Size: 33527 bytes
> >               Desc: image001.png
> >               URL:
> > <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d
> > 9a1123/attachment.png
> > <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20171207/2d
> > 9a1123/attachment.png> >
> >
> >               ------------------------------
> >
> >
> >       _______________________________________________
> >               Fuego mailing list
> >               Fuego@lists.linuxfoundation.org
> > <mailto:Fuego@lists.linuxfoundation.org>
> >               https://lists.linuxfoundation.org/mailman/listinfo/fuego
> > <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
> >
> >
> >               End of Fuego Digest, Vol 17, Issue 9
> >               ************************************
>
>

[-- Attachment #2: Type: text/html, Size: 28545 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
       [not found]       ` <CABehs3NKZkvc4nQ8qoR2+cF-HH94zS=67vLXjqCaeFr5urPOAA@mail.gmail.com>
@ 2018-03-23 14:52         ` dhinakar k
  2018-03-23 17:05           ` Tim.Bird
       [not found]           ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p8>
  0 siblings, 2 replies; 14+ messages in thread
From: dhinakar k @ 2018-03-23 14:52 UTC (permalink / raw)
  To: Tim.Bird; +Cc: fuego

[-- Attachment #1: Type: text/plain, Size: 18447 bytes --]

Hi Tim,

Thanks a lot for the suggestion.

Guilherme Camargo's patch to use cross-toolchains from Debian unstable
rather than from the Emdebian project did the trick and it works now.

Iam able to build and execute dbench, netperf, fis, ffsb and other tests
successful which were failing during build process because of '
Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity
check' issue.

Does it mean there is an issue in Emdebian toolchain?

Thanks much once again.

Regards,
Dhinakar

On 20 Mar 2018 7:15 pm, <Tim.Bird@sony.com> wrote:



> -----Original Message-----
> From: dhinakar k
> Thank you very much for your prompt reply.
>
> Anyone else in this forum can help?

I seem to recall working on this problem last year, but I don't recall the
details.
Guilherme Camargo just added a patch to use cross-toolchains from
Debian unstable rather than from the Emdebian project.

You might want to check out the latest fuego master repository
and try the 'fuego-ro/toolchains/install_cross_toolchain.sh arm64'
(inside the docker container), and see what happens when building
those tests.

Let me know if this helps.
 -- Tim

> Regards,
> Dhinakar
>
> On 15 Mar 2018 7:49 am, "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> <mailto:liuwl.fnst@cn.fujitsu.com> > wrote:
>
>
>       Hi Dhinakar
>
>
>
>       > Did you find any permanent fix to this issue?
>
>
>
>       Sorry, I didn’t use that toolchain any more.
>
>       Now, I’m using a yocto toolchain which can help me out.
>
>
>
>       Thanks.
>
>
>
>       Best regards
>
>       Liu
>
>
>
>       From: fuego-bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org>  [mailto:fuego-
> bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org> ] On Behalf Of dhinakar k
>       Sent: Thursday, March 15, 2018 9:46 AM
>       To: fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
>       Subject: Re: [Fuego] Configure: error: C preprocessor
"aarch64-linux-
> gnu-cpp" fails sanity check (netperf, dbench tests)
>
>
>
>       Hi Liu,
>
>       I am very sorry, somehow I missed out seeing your reply.
>
>       Thanks for your suggestion.
>
>
>
>       Since I missed seeing your reply, I managed it by commenting out the
> build part in fuego shell script and transferred the pre-compiled
binaries to
> the desired location.
>
>       I downloaded the latest linaro toolchain but it did not fix the
issue.
>
>       I also installed the arm64 cross toolchain inside the container
using
> the install shell script but it also did not fix the issue.
>
>       Did you find any permanent fix to this issue?
>
>       Regards,
>
>       Dhinakar
>
>
>
>       On Thu, Dec 7, 2017 at 3:51 PM, <fuego-
> request@lists.linuxfoundation.org <mailto:fuego-
> request@lists.linuxfoundation.org> > wrote:
>
>               Send Fuego mailing list submissions to
>                       fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
>
>               To subscribe or unsubscribe via the World Wide Web, visit
>                       https://lists.linuxfoundation.
org/mailman/listinfo/fuego
> <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
>               or, via email, send a message with subject or body 'help' to
>                       fuego-request@lists.linuxfoundation.org <mailto:
fuego-
> request@lists.linuxfoundation.org>
>
>               You can reach the person managing the list at
>                       fuego-owner@lists.linuxfoundation.org <mailto:fuego-
> owner@lists.linuxfoundation.org>
>
>               When replying, please edit your Subject line so it is more
> specific
>               than "Re: Contents of Fuego digest..."
>
>
>               Today's Topics:
>
>                  1. Re: Configure: error: C preprocessor
"aarch64-linux-gnu-
> cpp"
>                     fails sanity check (netperf, dbench tests) (Liu,
Wenlong)
>
>
>               ------------------------------------------------------------
----------
>
>               Message: 1
>               Date: Thu, 7 Dec 2017 10:21:06 +0000
>               From: "Liu, Wenlong" <liuwl.fnst@cn.fujitsu.com
> <mailto:liuwl.fnst@cn.fujitsu.com> >
>               To: "dhinakar.k@samsung.com
> <mailto:dhinakar.k@samsung.com> " <dhinakar.k@samsung.com
> <mailto:dhinakar.k@samsung.com> >,
>                       "fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org> "
> <fuego@lists.linuxfoundation.org <mailto:fuego@lists.linuxfoundation.org>
> >
>               Cc: "Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> "
> <Tim.Bird@sony.com <mailto:Tim.Bird@sony.com> >
>               Subject: Re: [Fuego] Configure: error: C preprocessor
>                       "aarch64-linux-gnu-cpp" fails sanity check (netperf,
> dbench tests)
>               Message-ID:
>
> <F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPEKD01.g
> 08.fujitsu.local
> <mailto:F40213214988A94A9DDBFC5F7146FC5E012C65BB24@G08CNEXMBPE
> KD01.g08.fujitsu.local> >
>
>               Content-Type: text/plain; charset="utf-8"
>
>               Hi dhinakar,
>
>
>
>               I think we just have the same situation.
>
>               About this issue, it seems that symbolic link
?aarch64-linux-
> gnu-cpp? missing for me(don?t know what the cause is yet).
>
>               Creating this symbolic link manually can solve this problem
> temporarily.
>
>
>
>               Hope that?s useful to you.
>
>
>
>               Best regards
>
>               Liu
>
>               From: fuego-bounces@lists.linuxfoundation.org
> <mailto:fuego-bounces@lists.linuxfoundation.org>  [mailto:fuego-
> bounces@lists.linuxfoundation.org <mailto:fuego-
> bounces@lists.linuxfoundation.org> ] On Behalf Of Dhinakar
> Kalyanasundaram
>               Sent: Thursday, November 30, 2017 10:34 PM
>               To: fuego@lists.linuxfoundation.org
> <mailto:fuego@lists.linuxfoundation.org>
>               Cc: Tim.Bird@sony.com <mailto:Tim.Bird@sony.com>
>               Subject: [Fuego] Configure: error: C preprocessor "aarch64-
> linux-gnu-cpp" fails sanity check (netperf, dbench tests)
>
>
>               Dear All,
>
>
>
>               I am using Fuego v1.2.1 (main branch not 'next'  branch).
>
>               While executing 'netperf', 'dbench' test etc. I am getting
> 'configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity
check '
> error.
>
>               I have pasted the error log below for reference.
>
>               The aarch64 tool chain has been installed inside the
container
> by executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64'
> command.
>
>               Is there anything else that I need to setup? Please let me
> know.
>
>
>
>               Also I see the below warning in most of the tests log.
>
>               ########################### WARNING
> ###############################
>               Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-
> Test.default.1.1/testlog.txt
>               -----
>
>               Why is it always referring to 'default.1.1' test? Is it for
results
> comparison & charting purpose?
>
>
>
>               ....
>
>               [buildzone] $ /bin/sh -xe
> /tmp/hudson7334983476305155012.sh
>               + export Reboot=false
>               + Reboot=false
>               + export Rebuild=false
>               + Rebuild=false
>               + export Target_PreCleanup=true
>               + Target_PreCleanup=true
>               + export Target_PostCleanup=true
>               + Target_PostCleanup=true
>               + export TESTDIR=Benchmark.netperf
>               + TESTDIR=Benchmark.netperf
>               + export TESTSPEC=default
>               + TESTSPEC=default
>               + timeout --signal=9 6m /bin/bash /fuego-
> core/engine/scripts/main.sh
>               Using nosyslogd.dist overlay
>               ##### doing fuego phase: pre_test ########
>               Logged in as user root
>               Firmware revision: 4.9.0+
>
>
>               01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75
>
>                             total        used        free      shared
buff/cache   available
>               Mem:        2342088       57228     2272632         208
   12228
> 2244820
>               Swap:             0           0           0
>
>               Filesystem      Size  Used Avail Use% Mounted on
>               /dev/root       7.2G  4.4G  2.5G  64% /
>               devtmpfs        337M     0  337M   0% /dev
>               tmpfs           1.2G     0  1.2G   0% /dev/shm
>               tmpfs           1.2G   52K  1.2G   1% /tmp
>               tmpfs           1.2G  156K  1.2G   1% /run
>
>               /dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
>               devtmpfs on /dev type devtmpfs
> (rw,relatime,size=344208k,nr_inodes=86052,mode=755)
>               proc on /proc type proc (rw,relatime)
>               devpts on /dev/pts type devpts
> (rw,relatime,gid=5,mode=620,ptmxmode=000)
>               tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
>               tmpfs on /tmp type tmpfs (rw,relatime)
>               tmpfs on /run type tmpfs
> (rw,nosuid,nodev,relatime,mode=755)
>               sysfs on /sys type sysfs (rw,relatime)
>
>               BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.
>
>               Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-
> e PATTERN.../-f FILE [FILE]...
>
>               Search for PATTERN in FILEs (or stdin)
>
>               -H Add 'filename:' prefix
>               -h Do not add 'filename:' prefix
>               -n Add 'line_no:' prefix
>               -l Show only names of files that match
>               -L Show only names of files that don't match
>               -c Show only count of matching lines
>               -o Show only the matching part of line
>               -q Quiet. Return 0 if PATTERN is found, 1 otherwise
>               -v Select non-matching lines
>               -s Suppress open and read errors
>               -r Recurse
>               -i Ignore case
>               -w Match whole words only
>               -x Match whole lines only
>               -F PATTERN is a literal (not regexp)
>               -E PATTERN is an extended regexp
>               -m N Match up to N times per file
>               -A N Print N lines of trailing context
>               -B N Print N lines of leading context
>               -C N Same as '-A N -B N'
>               -e PTRN Pattern to match
>               -f FILE Read pattern from file
>
>               [ 5388.605500] sh (2553): drop_caches: 3
>
>               ##### doing fuego phase: build ########
>
>               Unpacking ../netperf/netperf-2.6.0.tar.bz2
>               configure: loading cache config.cache
>               checking build system type... x86_64-unknown-linux-gnu
>               checking host system type... aarch64-unknown-linux-gnu
>               checking target system type... aarch64-unknown-linux-gnu
>               checking for a BSD-compatible install... /usr/bin/install -c
>               checking whether build environment is sane... yes
>               checking for aarch64-linux-gnu-strip...
aarch64-linux-gnu-strip
>               checking for a thread-safe mkdir -p... /bin/mkdir -p
>               checking for gawk... no
>               checking for mawk... mawk
>               checking whether make sets $(MAKE)... yes
>               checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
>               checking whether the C compiler works... yes
>               checking for C compiler default output file name... a.out
>               checking for suffix of executables...
>               checking whether we are cross compiling... yes
>               checking for suffix of object files... o
>               checking whether we are using the GNU C compiler... yes
>               checking whether aarch64-linux-gnu-gcc accepts -g... yes
>               checking for aarch64-linux-gnu-gcc option to accept ISO
C89...
> none needed
>               checking for style of include used by make... GNU
>               checking dependency style of aarch64-linux-gnu-gcc... gcc3
>               checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-
> ranlib
>               checking for an ANSI C-conforming const... yes
>               checking for main in -lm... yes
>               checking how to run the C preprocessor... aarch64-linux-gnu-
> cpp
>               configure: error: in `/fuego-rw/buildzone/TRAV-Sanity-
> Test.default.Benchmark.netperf-aarch64':
>               configure: error: C preprocessor "aarch64-linux-gnu-cpp"
fails
> sanity check
>               See `config.log' for more details
>               in signal_handler
>               Teardown board link
>               WARNING: program returned exit code
>               Log evaluation may be invalid
>               Going to check 1 fail cases for TRAV-Sanity-
> Test.default.Benchmark.netperf
>               grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt: No such file or directory
>               No fail cases detected for TRAV-Sanity-
> Test.default.Benchmark.netperf
>               running python with
> PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gam
> es
>               ########################### WARNING
> ###############################
>               Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt
>               -----
>               matches: None
>               WARNING: missing or faulty criteria.json file (/fuego-
> core/engine/tests/Benchmark.netperf/criteria.json), looking for
> reference.log
>               converting reference.log for test netperf
>               criteria_data= {'schema_version': '1.0', 'criteria':
[{'reference':
> {'operator': 'le', 'value': 10000000.0}, 'tguid':
> 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge',
> 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net
> <http://default.MIGRATED_TCP_MAERTS.net> '}, {'reference': {'operator':
> 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.cpu'},
> {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid':
> 'default.MIGRATED_TCP_STREAM.net
> <http://default.MIGRATED_TCP_STREAM.net> '}]}
>               No reference.json available
>               ref={'test_sets': []}
>               Applying criterion {'max_fail': 0, 'tguid':
'Benchmark.netperf'}
>               Writing run data to /fuego-
> rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json
>               reference.json not available
>               Writing merged results to  /fuego-
> rw/logs/Benchmark.netperf/results.json
>               Writing flat results to /fuego-
> rw/logs/Benchmark.netperf/flat_plot_data.txt
>               chart_config.json not available or is wrong format, using
> default values
>               Writing chart data to /fuego-
> rw/logs/Benchmark.netperf/flot_chart_data.json
>               ERROR: results did not satisfy the threshold
>               Build step 'Execute shell' marked build as failure
>               [description-setter] Description set:  <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/testlog.txt">testlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/run.json">run.json</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/consolelog.txt">fuegolog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/devlog.txt">devlog</a> <a
> href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-
> Test.default.1.1/prolog.sh">prolog.sh</a>
>               Finished: FAILURE
>
>
>
>               Regards,
>
>               Dhinakar,
>
>               Senior Technical Manager,
>
>               2-07-526, Phoenix Building,
>
>               +91-9902007650
>
>               Samsung Research Institute, Bangalore.
>
>               [cid:image001.png@01D36F84.A9EFAF20]
>
>               [Web Bug from
> http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinak
> ar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYTk
> wMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPWZ
> 1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYT
> kwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPW
> Z1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_> ]
>
>
>               -------------- next part --------------
>               An HTML attachment was scrubbed...
>               URL:
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.html
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.html> >
>               -------------- next part --------------
>               A non-text attachment was scrubbed...
>               Name: image001.png
>               Type: image/png
>               Size: 33527 bytes
>               Desc: image001.png
>               URL:
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.png
> <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20171207/2d
> 9a1123/attachment.png> >
>
>               ------------------------------
>
>
>       _______________________________________________
>               Fuego mailing list
>               Fuego@lists.linuxfoundation.org
> <mailto:Fuego@lists.linuxfoundation.org>
>               https://lists.linuxfoundation.org/mailman/listinfo/fuego
> <https://lists.linuxfoundation.org/mailman/listinfo/fuego>
>
>
>               End of Fuego Digest, Vol 17, Issue 9
>               ************************************

[-- Attachment #2: Type: text/html, Size: 30330 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-23 14:52         ` dhinakar k
@ 2018-03-23 17:05           ` Tim.Bird
       [not found]           ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p8>
  1 sibling, 0 replies; 14+ messages in thread
From: Tim.Bird @ 2018-03-23 17:05 UTC (permalink / raw)
  To: dhinakar.k; +Cc: fuego



> -----Original Message-----
> From: dhinakar k [mailto:dhinakar.k@gmail.com]
> 
> Hi Tim,
> 
> Thanks a lot for the suggestion.
> 
> Guilherme Camargo's patch to use cross-toolchains from Debian unstable
> rather than from the Emdebian project did the trick and it works now.
> 
> 
> Iam able to build and execute dbench, netperf, fis, ffsb and other tests
> successful which were failing during build process because of '
> Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check'
> issue.

Thanks for reporting back the status.  Let us know if any tests behave strangely
with the different toolchains.

I am a bit worried that you'll run into some issues with this toolchain.
If I recall correctly, you are not running Debian on your board, right?
If not, there should be a toolchain available from your distribution provider,
or that can be built from OpenEmbedded, the YoctoProject, or buildroot
(whichever tool you are using to build the Linux distribution for your board).

If you have hand-assembled your own distribution manually, then you should
use whatever toolchain you used to build the rest of the distribution. 

The specific toolchain for your distribution is always the preferred one to 
use for building additional software (including test programs) for your board.

> 
> 
> Does it mean there is an issue in Emdebian toolchain?

Yes.  Our plan is to use regular Debian cross toolchains, rather than
EmDebian.  Emdebian seems to be an unmaintained project.
 -- Tim



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
       [not found]           ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p8>
@ 2018-03-24  7:28             ` Dhinakar Kalyanasundaram
  2018-03-26 23:29               ` Tim.Bird
       [not found]               ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p3>
  0 siblings, 2 replies; 14+ messages in thread
From: Dhinakar Kalyanasundaram @ 2018-03-24  7:28 UTC (permalink / raw)
  To: Tim.Bird; +Cc: fuego, dhinakar.k

[-- Attachment #1: Type: text/html, Size: 6638 bytes --]

[-- Attachment #2: 201602111742151_N3WZA6X7.png --]
[-- Type: image/png, Size: 33527 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-24  7:28             ` Dhinakar Kalyanasundaram
@ 2018-03-26 23:29               ` Tim.Bird
  2018-03-26 23:53                 ` Daniel Sangorrin
       [not found]               ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p3>
  1 sibling, 1 reply; 14+ messages in thread
From: Tim.Bird @ 2018-03-26 23:29 UTC (permalink / raw)
  To: dhinakar.k; +Cc: fuego, dhinakar.k



> -----Original Message-----
> From: Dhinakar Kalyanasundaram 
> Hi Tim,
> 
> Thanks for reporting back the status.  Let us know if any tests behave
> strangely
> with the different toolchains.
> 
> ----> Sure I will keep you informed on this
> 
> 
> 
> I am running kernel, dtb images built using Linaro toolchain and RFS is from
> Buildroot.
> 
> Earlier I used to use my own shell script configured as given below.
> 
> But later I started using the toolchain installed inside the docker container.

Interesting.  Does buildroot produce an SDK or toolchain?

> I am not sure if the below script is correct/enough or do I need to do the
> settings for all the FLAGS as well.

Your call to 'export_tools' will set the other required environment
variables.

The biggest problems we see with mis-matched toolchains and distros
is with libraries.  Some tests require libraries that the SDK or distro on the
board doesn't provide.

If the tests are building OK and the test binaries are running OK on the board,
I think you're in good shape.  It's possible, but much less likely, that a
toolchain mismatch will produce subtle errors.  Usually the build fails or
the test execution (in test_run()) fails.

 -- Tim


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-26 23:29               ` Tim.Bird
@ 2018-03-26 23:53                 ` Daniel Sangorrin
  2018-03-27  0:08                   ` Tim.Bird
  0 siblings, 1 reply; 14+ messages in thread
From: Daniel Sangorrin @ 2018-03-26 23:53 UTC (permalink / raw)
  To: Tim.Bird, dhinakar.k; +Cc: fuego, dhinakar.k

> -----Original Message-----
> From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.linuxfoundation.org] On Behalf Of Tim.Bird@sony.com
> > -----Original Message-----
> > From: Dhinakar Kalyanasundaram
> > Hi Tim,
> >
> > Thanks for reporting back the status.  Let us know if any tests behave
> > strangely
> > with the different toolchains.
> >
> > ----> Sure I will keep you informed on this
> >
> >
> >
> > I am running kernel, dtb images built using Linaro toolchain and RFS is from
> > Buildroot.
> >
> > Earlier I used to use my own shell script configured as given below.
> >
> > But later I started using the toolchain installed inside the docker container.
> 
> Interesting.  Does buildroot produce an SDK or toolchain?
> 
> > I am not sure if the below script is correct/enough or do I need to do the
> > settings for all the FLAGS as well.
> 
> Your call to 'export_tools' will set the other required environment
> variables.
> 
> The biggest problems we see with mis-matched toolchains and distros
> is with libraries.  Some tests require libraries that the SDK or distro on the
> board doesn't provide.
> 
> If the tests are building OK and the test binaries are running OK on the board,
> I think you're in good shape.  It's possible, but much less likely, that a
> toolchain mismatch will produce subtle errors.  Usually the build fails or
> the test execution (in test_run()) fails.

I see two solutions to the problems with toolchains (people using mis-matching toolchains,
or lacking the libraries to build/run the tests):
- Modify all fuego_test.sh files (as in dbench) to use the test binaries existing on the target preferentially.
  This way people could add their tests to the filesystem (e.g. with yocto or debian) and do not care about
  the kind of more advanced SDK setup. We will probably need to check that the fuego_test.sh/parser.py
  support the test version installed on the target.
- When building a test, try to use static linking to avoid library mismatches as much as possible (as in iperf3).

Thanks,
Daniel



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2018-03-26 23:53                 ` Daniel Sangorrin
@ 2018-03-27  0:08                   ` Tim.Bird
  0 siblings, 0 replies; 14+ messages in thread
From: Tim.Bird @ 2018-03-27  0:08 UTC (permalink / raw)
  To: daniel.sangorrin, dhinakar.k; +Cc: fuego, dhinakar.k



> -----Original Message-----
> From: Daniel Sangorrin on Monday, March 26, 2018 4:53 PM
> > -----Original Message-----
> > From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-
> bounces@lists.linuxfoundation.org] On Behalf Of Tim.Bird@sony.com
> > > -----Original Message-----
> > > From: Dhinakar Kalyanasundaram
> > > Hi Tim,
> > >
> > > Thanks for reporting back the status.  Let us know if any tests behave
> > > strangely
> > > with the different toolchains.
> > >
> > > ----> Sure I will keep you informed on this
> > >
> > > I am running kernel, dtb images built using Linaro toolchain and RFS is
> from
> > > Buildroot.
> > >
> > > Earlier I used to use my own shell script configured as given below.
> > >
> > > But later I started using the toolchain installed inside the docker
> container.
> >
> > Interesting.  Does buildroot produce an SDK or toolchain?
> >
> > > I am not sure if the below script is correct/enough or do I need to do the
> > > settings for all the FLAGS as well.
> >
> > Your call to 'export_tools' will set the other required environment
> > variables.
> >
> > The biggest problems we see with mis-matched toolchains and distros
> > is with libraries.  Some tests require libraries that the SDK or distro on the
> > board doesn't provide.
> >
> > If the tests are building OK and the test binaries are running OK on the
> board,
> > I think you're in good shape.  It's possible, but much less likely, that a
> > toolchain mismatch will produce subtle errors.  Usually the build fails or
> > the test execution (in test_run()) fails.
> 
> I see two solutions to the problems with toolchains (people using mis-
> matching toolchains,
> or lacking the libraries to build/run the tests):
> - Modify all fuego_test.sh files (as in dbench) to use the test binaries existing
> on the target preferentially.
>   This way people could add their tests to the filesystem (e.g. with yocto or
> debian) and do not care about
>   the kind of more advanced SDK setup. We will probably need to check that
> the fuego_test.sh/parser.py
>   support the test version installed on the target.
Yeah.  Siemens asked quite a while ago to be able to use test programs already
in the filesystem.  If we have something like a single program name, then
we can do something in pre-test to check for that program name, and if
present have Fuego avoid the build and deploy.   This can be done more simply
than how we did this for LTP, as there are less other dependencies for other
tests.

What I envision is basically the same operations you did in dbench, but
maybe a little bit more automatic.  Like maybe we declare:
TEST_PROGRAM=dbench
and the dependency system checks for it automatically.
And the build and deploy systems are short-circuited automatically, if it's
found on the board.

But the second issue you raise - making sure that the fuego test works
correctly with the test program already on target, is important.  Doing so
may be problematic in the general case.  If we don't
do good checking we may run into subtle bugs.  But, checking should
not be too difficult either, for most tests.

> - When building a test, try to use static linking to avoid library mismatches as
> much as possible (as in iperf3).


Agreed.

This is good practice for tests in general, and we should encourage it and
use build instructions that do static linking when we can.
A test should have as few dependencies as possible on the target (besides
the things it is actually testing).
 -- Tim


^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
       [not found]               ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p3>
@ 2018-03-27  4:08                 ` Dhinakar Kalyanasundaram
  0 siblings, 0 replies; 14+ messages in thread
From: Dhinakar Kalyanasundaram @ 2018-03-27  4:08 UTC (permalink / raw)
  To: Tim.Bird; +Cc: fuego, dhinakar.k

[-- Attachment #1: Type: text/html, Size: 3579 bytes --]

[-- Attachment #2: 201602111742151_N3WZA6X7.png --]
[-- Type: image/png, Size: 33527 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
  2017-11-30 14:34 ` Dhinakar Kalyanasundaram
@ 2017-12-07 10:21   ` Liu, Wenlong
  0 siblings, 0 replies; 14+ messages in thread
From: Liu, Wenlong @ 2017-12-07 10:21 UTC (permalink / raw)
  To: dhinakar.k, fuego; +Cc: Tim.Bird


[-- Attachment #1.1: Type: text/plain, Size: 8645 bytes --]

Hi dhinakar,



I think we just have the same situation.

About this issue, it seems that symbolic link “aarch64-linux-gnu-cpp” missing for me(don’t know what the cause is yet).

Creating this symbolic link manually can solve this problem temporarily.



Hope that’s useful to you.



Best regards

Liu

From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.linuxfoundation.org] On Behalf Of Dhinakar Kalyanasundaram
Sent: Thursday, November 30, 2017 10:34 PM
To: fuego@lists.linuxfoundation.org
Cc: Tim.Bird@sony.com
Subject: [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)


Dear All,



I am using Fuego v1.2.1 (main branch not 'next'  branch).

While executing 'netperf', 'dbench' test etc. I am getting 'configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check ' error.

I have pasted the error log below for reference.

The aarch64 tool chain has been installed inside the container by executing the '/fuego-ro/toolchains/install_cross_toolchain.sh arm64' command.

Is there anything else that I need to setup? Please let me know.



Also I see the below warning in most of the tests log.

########################### WARNING ###############################
Can't open /fuego-rw/logs/Benchmark.dbench/TRAV-Sanity-Test.default.1.1/testlog.txt
-----

Why is it always referring to 'default.1.1' test? Is it for results comparison & charting purpose?



....

[buildzone] $ /bin/sh -xe /tmp/hudson7334983476305155012.sh
+ export Reboot=false
+ Reboot=false
+ export Rebuild=false
+ Rebuild=false
+ export Target_PreCleanup=true
+ Target_PreCleanup=true
+ export Target_PostCleanup=true
+ Target_PostCleanup=true
+ export TESTDIR=Benchmark.netperf
+ TESTDIR=Benchmark.netperf
+ export TESTSPEC=default
+ TESTSPEC=default
+ timeout --signal=9 6m /bin/bash /fuego-core/engine/scripts/main.sh
Using nosyslogd.dist overlay
##### doing fuego phase: pre_test ########
Logged in as user root
Firmware revision: 4.9.0+


01:29:46 up  1:29,  1 user,  load average: 3.65, 1.92, 0.75

              total        used        free      shared  buff/cache   available
Mem:        2342088       57228     2272632         208       12228     2244820
Swap:             0           0           0

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       7.2G  4.4G  2.5G  64% /
devtmpfs        337M     0  337M   0% /dev
tmpfs           1.2G     0  1.2G   0% /dev/shm
tmpfs           1.2G   52K  1.2G   1% /tmp
tmpfs           1.2G  156K  1.2G   1% /run

/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=344208k,nr_inodes=86052,mode=755)
proc on /proc type proc (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=777)
tmpfs on /tmp type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
sysfs on /sys type sysfs (rw,relatime)

BusyBox v1.26.2 (2017-05-05 12:57:46 IST) multi-call binary.

Usage: grep [-HhnlLoqvsriwFE] [-m N] [-A/B/C N] PATTERN/-e PATTERN.../-f FILE [FILE]...

Search for PATTERN in FILEs (or stdin)

-H Add 'filename:' prefix
-h Do not add 'filename:' prefix
-n Add 'line_no:' prefix
-l Show only names of files that match
-L Show only names of files that don't match
-c Show only count of matching lines
-o Show only the matching part of line
-q Quiet. Return 0 if PATTERN is found, 1 otherwise
-v Select non-matching lines
-s Suppress open and read errors
-r Recurse
-i Ignore case
-w Match whole words only
-x Match whole lines only
-F PATTERN is a literal (not regexp)
-E PATTERN is an extended regexp
-m N Match up to N times per file
-A N Print N lines of trailing context
-B N Print N lines of leading context
-C N Same as '-A N -B N'
-e PTRN Pattern to match
-f FILE Read pattern from file

[ 5388.605500] sh (2553): drop_caches: 3

##### doing fuego phase: build ########

Unpacking ../netperf/netperf-2.6.0.tar.bz2
configure: loading cache config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking target system type... aarch64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for aarch64-linux-gnu-strip... aarch64-linux-gnu-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether aarch64-linux-gnu-gcc accepts -g... yes
checking for aarch64-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of aarch64-linux-gnu-gcc... gcc3
checking for aarch64-linux-gnu-ranlib... aarch64-linux-gnu-ranlib
checking for an ANSI C-conforming const... yes
checking for main in -lm... yes
checking how to run the C preprocessor... aarch64-linux-gnu-cpp
configure: error: in `/fuego-rw/buildzone/TRAV-Sanity-Test.default.Benchmark.netperf-aarch64':
configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check
See `config.log' for more details
in signal_handler
Teardown board link
WARNING: program returned exit code
Log evaluation may be invalid
Going to check 1 fail cases for TRAV-Sanity-Test.default.Benchmark.netperf
grep: /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt: No such file or directory
No fail cases detected for TRAV-Sanity-Test.default.Benchmark.netperf
running python with PATH=/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
########################### WARNING ###############################
Can't open /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt
-----
matches: None
WARNING: missing or faulty criteria.json file (/fuego-core/engine/tests/Benchmark.netperf/criteria.json), looking for reference.log
converting reference.log for test netperf
criteria_data= {'schema_version': '1.0', 'criteria': [{'reference': {'operator': 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.cpu'}, {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_MAERTS.net'}, {'reference': {'operator': 'le', 'value': 10000000.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.cpu'}, {'reference': {'operator': 'ge', 'value': 0.0}, 'tguid': 'default.MIGRATED_TCP_STREAM.net'}]}
No reference.json available
ref={'test_sets': []}
Applying criterion {'max_fail': 0, 'tguid': 'Benchmark.netperf'}
Writing run data to /fuego-rw/logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json
reference.json not available
Writing merged results to  /fuego-rw/logs/Benchmark.netperf/results.json
Writing flat results to /fuego-rw/logs/Benchmark.netperf/flat_plot_data.txt
chart_config.json not available or is wrong format, using default values
Writing chart data to /fuego-rw/logs/Benchmark.netperf/flot_chart_data.json
ERROR: results did not satisfy the threshold
Build step 'Execute shell' marked build as failure
[description-setter] Description set:  <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/testlog.txt">testlog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/run.json">run.json</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/consolelog.txt">fuegolog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/devlog.txt">devlog</a> <a href="/storm/userContent/fuego.logs/Benchmark.netperf/TRAV-Sanity-Test.default.1.1/prolog.sh">prolog.sh</a>
Finished: FAILURE



Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

[cid:image001.png@01D36F84.A9EFAF20]

[Web Bug from http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhinakar.k&do=bWFpbElEPTIwMTcxMTMwMTQzNDA4ZXBjbXM1cDc3NDc0NDljYTkwMjUyNmQ2MTg2MmI4MmQyZmQyYjg3YSZyZWNpcGllbnRBZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_]



[-- Attachment #1.2: Type: text/html, Size: 16565 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 33527 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests)
       [not found] <CGME20171130143408epcms5p7747449ca902526d61862b82d2fd2b87a@epcms5p7>
@ 2017-11-30 14:34 ` Dhinakar Kalyanasundaram
  2017-12-07 10:21   ` Liu, Wenlong
  0 siblings, 1 reply; 14+ messages in thread
From: Dhinakar Kalyanasundaram @ 2017-11-30 14:34 UTC (permalink / raw)
  To: fuego; +Cc: Tim.Bird

[-- Attachment #1: Type: text/html, Size: 10533 bytes --]

[-- Attachment #2: 201602111742151_N3WZA6X7.png --]
[-- Type: image/png, Size: 33527 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2018-03-27  4:08 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-15  1:46 [Fuego] Configure: error: C preprocessor "aarch64-linux-gnu-cpp" fails sanity check (netperf, dbench tests) dhinakar k
2018-03-15  2:19 ` Liu, Wenlong
2018-03-15  2:46   ` dhinakar k
2018-03-20 13:44     ` Tim.Bird
2018-03-22 13:59       ` dhinakar k
     [not found]       ` <CABehs3NKZkvc4nQ8qoR2+cF-HH94zS=67vLXjqCaeFr5urPOAA@mail.gmail.com>
2018-03-23 14:52         ` dhinakar k
2018-03-23 17:05           ` Tim.Bird
     [not found]           ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p8>
2018-03-24  7:28             ` Dhinakar Kalyanasundaram
2018-03-26 23:29               ` Tim.Bird
2018-03-26 23:53                 ` Daniel Sangorrin
2018-03-27  0:08                   ` Tim.Bird
     [not found]               ` <CGME20180323170607epcas4p13a2de3e3438c8e8ddd8e0898cde3ca41@epcms5p3>
2018-03-27  4:08                 ` Dhinakar Kalyanasundaram
     [not found] <CGME20171130143408epcms5p7747449ca902526d61862b82d2fd2b87a@epcms5p7>
2017-11-30 14:34 ` Dhinakar Kalyanasundaram
2017-12-07 10:21   ` Liu, Wenlong

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.