All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: Joe MacDonald <Joe_MacDonald@mentor.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] waf-cross-answers: Fix faulty link cross-answers-mipsel.txt
Date: Mon, 11 Apr 2016 15:33:47 +0200	[thread overview]
Message-ID: <570BA7BB.5090504@topic.nl> (raw)
In-Reply-To: <20160406171431.GB5060@mentor.com>

On 06-04-16 19:14, Joe MacDonald wrote:
> Hi Mike,
>
> [Re: [PATCH] waf-cross-answers: Fix faulty link cross-answers-mipsel.txt] On 16.04.05 (Tue 08:17) Mike Looijmans wrote:
>
>> Just a reminder that currently "waf" is broken and still won't work on
>> mipsel platforms without this bugfix.
>
> I merged this for you and pushed it a few minutes ago.  I don't have any
> MIPS hardware to test this on but I'm trusting that since you're
> reporting it's a build failure that validating for the Edgerouter is a
> valid test case.  Is that true?

Don't know that particular box, but if it failed to build (because it's mipsel 
and reports a missing file) before this patch, then yes, that's okay as a test.

M.


>
>>
>>
>> On 02-04-16 10:22, Mike Looijmans wrote:
>>> Apparently something was wrong in the patch "waf-cross-answers:
>>> Add cross-answers-mipsel.txt". and it created a dead symlink.
>>> Solve it by just copying the cross-answers-mips.txt instead of
>>> linking it.
>>>
>>> Fixes: 0898fb01ccea229cb0c64796b62f20a7c596ac0b
>>>
>>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>>> ---
>>>   .../waf-cross-answers/cross-answers-mipsel.txt     | 40 +++++++++++++++++++++-
>>>   1 file changed, 39 insertions(+), 1 deletion(-)
>>>   mode change 120000 => 100644 meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt
>>>
>>> diff --git a/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt b/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt
>>> deleted file mode 120000
>>> index 59b4337..0000000
>>> --- a/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt
>>> +++ /dev/null
>>> @@ -1 +0,0 @@
>>> -cross-answers-mips.txt
>>> diff --git a/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt b/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt
>>> new file mode 100644
>>> index 0000000..18bfa02
>>> --- /dev/null
>>> +++ b/meta-networking/files/waf-cross-answers/cross-answers-mipsel.txt
>>> @@ -0,0 +1,39 @@
>>> +Checking uname sysname type: "Linux"
>>> +Checking uname version type: "# Wed May 20 10:34:39 UTC 2015"
>>> +Checking simple C program: "hello world"
>>> +rpath library support: OK
>>> +-Wl,--version-script support: OK
>>> +Checking getconf LFS_CFLAGS: NO
>>> +Checking correct behavior of strtoll: NO
>>> +Checking for working strptime: OK
>>> +Checking for C99 vsnprintf: "1"
>>> +Checking for HAVE_SHARED_MMAP: OK
>>> +Checking for HAVE_MREMAP: OK
>>> +Checking for HAVE_SECURE_MKSTEMP: OK
>>> +Checking for HAVE_IFACE_GETIFADDRS: NO
>>> +Checking for HAVE_IFACE_IFCONF: NO
>>> +Checking for HAVE_IFACE_IFREQ: NO
>>> +Checking for large file support without additional flags: NO
>>> +Checking for -D_FILE_OFFSET_BITS=64: OK
>>> +Checking for HAVE_INCOHERENT_MMAP: NO
>>> +Checking value of NSIG: "128"
>>> +Checking value of _NSIG: "128"
>>> +Checking value of SIGRTMAX: "127"
>>> +Checking value of SIGRTMIN: "34"
>>> +Checking whether the WRFILE -keytab is supported: OK
>>> +Checking for kernel change notify support: OK
>>> +Checking for Linux kernel oplocks: OK
>>> +Checking for kernel share modes: OK
>>> +Checking whether POSIX capabilities are available: OK
>>> +Checking if can we convert from CP850 to UCS-2LE: OK
>>> +Checking if can we convert from UTF-8 to UCS-2LE: OK
>>> +vfs_fileid checking for statfs() and struct statfs.f_fsid: OK
>>> +Checking whether we can use Linux thread-specific credentials: OK
>>> +Checking whether fcntl locking is available: OK
>>> +Checking for the maximum value of the 'time_t' type: NO
>>> +Checking whether the realpath function allows a NULL argument: OK
>>> +Checking for ftruncate extend: OK
>>> +getcwd takes a NULL argument: OK
>>> +Checking for small off_t: NO
>>> +Checking whether blkcnt_t is 32 bit: NO
>>> +Checking whether blkcnt_t is 64 bit: OK
>>>
>>
>>
>>
>> Kind regards,
>>
>> Mike Looijmans
>> System Expert
>>
>> TOPIC Embedded Products
>> Eindhovenseweg 32-C, NL-5683 KH Best
>> Postbus 440, NL-5680 AK Best
>> Telefoon: +31 (0) 499 33 69 79
>> E-mail: mike.looijmans@topicproducts.com
>> Website: www.topicproducts.com
>>
>> Please consider the environment before printing this e-mail
>>
>>
>>
>>
>>
>



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail







  reply	other threads:[~2016-04-12  0:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02  8:22 [PATCH] waf-cross-answers: Fix faulty link cross-answers-mipsel.txt Mike Looijmans
2016-04-05  6:17 ` Mike Looijmans
2016-04-06 17:14   ` Joe MacDonald
2016-04-11 13:33     ` Mike Looijmans [this message]
2016-04-11 13:42       ` Joe MacDonald

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=570BA7BB.5090504@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=Joe_MacDonald@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.