From: Guenter Roeck <linux@roeck-us.net>
To: Nick Krause <xerofoify@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: jslaby@suse.cz,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: shx3_defconfig Fails
Date: Mon, 07 Jul 2014 21:50:58 -0700 [thread overview]
Message-ID: <53BB78B2.1020401@roeck-us.net> (raw)
In-Reply-To: <CAPDOMVg+HGpvVYw1VAvaMFK7eXwKh-qZZfObzgzLCFtmQV3B2w@mail.gmail.com>
On 07/07/2014 09:29 PM, Nick Krause wrote:
> Guenter Roeck work on Tue, Jul 8, 2014 at 12:00 AM
> Subject: Re: shx3_defconfig Fails
>
> On 07/07/2014 08:32 PM, Greg KH wrote:
>>
>> On Mon, Jul 07, 2014 at 11:04:23PM -0400, Nick Krause wrote:
>>>
>>> Hey Greg and others,
>>> The build, shx3_defconfig seems to be failing.
>>
>>
>> In what kernel version?
>>
>> Has it ever worked?
>>
>> Why not ask the maintainer of that arch about it? I doubt many people
>> ever use defconfig files anymore...
>>
>
> Works in mainline for me. And, for the record, I use lots of defconfig files
> (144 or so of them) for my build tests, so there is at least one user :-)
>
> Cheers,
> Guenter
>
> Still fails in the the same way. I am using the latest git tree.
> Cheers Nick
>
From your other errors I start wondering if you use dash or some other non-bash
shell and some dash-incompatibility creeped into the kernel build (again).
Guenter
next prev parent reply other threads:[~2014-07-08 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 3:04 shx3_defconfig Fails Nick Krause
2014-07-08 3:32 ` Greg KH
2014-07-08 4:00 ` Guenter Roeck
2014-07-08 4:29 ` Fwd: " Nick Krause
2014-07-08 4:46 ` Guenter Roeck
2014-07-08 4:50 ` Guenter Roeck [this message]
2014-07-08 5:07 ` Fwd: " Nick Krause
[not found] ` <CAPDOMVjfuDmdkASHTdO9CdzZbHHoRi9ZY2VXLeb3=aPywhsfWw@mail.gmail.com>
2014-07-08 5:13 ` Nick Krause
2014-07-08 5:18 ` Guenter Roeck
2014-07-08 5:39 ` Fwd: " Nick Krause
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=53BB78B2.1020401@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox