All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: "$rik@nth " <srikanth007m@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP make failed
Date: Wed, 29 Jul 2015 17:29:49 +0200	[thread overview]
Message-ID: <20150729152949.GA6478@rei.suse.de> (raw)
In-Reply-To: <CANKSX+ETp0jdXp+zSUtUPn8SWUQaCh1bETYzcpF_C8kZpPtGdQ@mail.gmail.com>

Hi!
> arm-linux-gnueabi-gcc -static -g -O2 -fno-strict-aliasing -pipe -Wall -W -static -Wold-style-definition   -I/local/mnt2/workspace2/LTP/ltp-full-20150420/testcases/kernel/lib/../include -I../../../include -I../../../include  -c -o numa_helper.o numa_helper.c
> numa_helper.c: In function ??get_nodemask_allnodes??:
> numa_helper.c:68:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> numa_helper.c:71:4: warning: implicit declaration of function ??nodemask_set?? [-Wimplicit-function-declaration]
> numa_helper.c: In function ??cpumask_has_cpus??:
> numa_helper.c:107:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> numa_helper.c: In function ??filter_nodemask_cpu??:
> numa_helper.c:125:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> numa_helper.c:126:3: warning: implicit declaration of function ??nodemask_isset?? [-Wimplicit-function-declaration]
> numa_helper.c:133:5: warning: implicit declaration of function ??nodemask_clr?? [-Wimplicit-function-declaration]
> numa_helper.c: In function ??get_allowed_nodes_arr??:
> numa_helper.c:190:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> if [ -z "numa_helper.o" ] ; then \
>                 echo "Cowardly refusing to create empty archive"; \
>                 exit 1; \
>         fi
> arm-linux-gnueabi-ar -rc "/prj/vlsi/tools/libraries" numa_helper.o
> arm-linux-gnueabi-ar: /prj/vlsi/tools/libraries: No such file or directory
> make: *** [/prj/vlsi/tools/libraries] Error 1

Now this is pretty much random filesystem patch.

This looks like a hardware/kernel bug to me.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2015-07-29 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 13:32 [LTP] LTP make failed $rik@nth 
2015-07-29 14:30 ` Jan Stancek
2015-07-29 14:45 ` Cyril Hrubis
     [not found]   ` <CANKSX+ETp0jdXp+zSUtUPn8SWUQaCh1bETYzcpF_C8kZpPtGdQ@mail.gmail.com>
2015-07-29 15:29     ` Cyril Hrubis [this message]
     [not found]       ` <1186607709.563342.1438184803657.JavaMail.zimbra@redhat.com>
2015-07-29 15:50         ` Cyril Hrubis
     [not found]           ` <CANKSX+EukvUBmjMf7TMxTzcsMXmzfGb+FYqrdo7vKnEiLb6wyg@mail.gmail.com>
2015-07-29 19:45             ` Cyril Hrubis
     [not found]               ` <CANKSX+FRJcg3xmc2BbWiDzmSqT2NC+hQib-UsWA4yoWTq8fB3g@mail.gmail.com>
2015-07-30  7:45                 ` Cyril Hrubis
2015-07-30  7:51                 ` Li Wang
2015-07-30 16:25                   ` $rik@nth 
2015-07-30 16:33                     ` Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150729152949.GA6478@rei.suse.de \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=srikanth007m@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.