From: Michal Marek <mmarek@suse.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org, mmarek@suse.cz,
joe@perches.com, lede-dev@lists.infradead.org,
openwrt-devel@lists.openwrt.org
Subject: Re: gen_initramfs_list.sh escaping problem or stale dependency file?
Date: Fri, 23 Sep 2016 09:05:17 +0200 [thread overview]
Message-ID: <ef840fed-065a-7b03-580e-66add0d89f59@suse.com> (raw)
In-Reply-To: <7db977f9-c9fa-4ae6-de75-834513a2d367@gmail.com>
On 2016-09-19 22:00, Florian Fainelli wrote:
> On 09/13/2016 12:24 AM, Michal Marek wrote:
>> On Mon, Sep 12, 2016 at 05:12:15PM -0700, Florian Fainelli wrote:
>>> Hi,
>>>
>>> I have a root filesystem embedding filenames that look like these:
>>>
>>> /lib/data/<vid>:<pid>
>>>
>>> these are essentially files that can be matched against an USB
>>> vendor/product id in an easy way.
>>>
>>> Now, the fun part is that this is only a problem when doing the
>>> following (using OpenWrt/LEDE as a build system):
>>>
>>> 1:
>>> - set CONFIG_INITRAMFS_SOURCE=""
>>> - build kernel modules
>>> - build my user-space tools
>>> - build the kernel image
>>> - reconfigure the kernel to now use an initramfs
>>> - build the kernel w/ initramfs
>>>
>>> and then back to step 1 with the kernel build, would I hit this error:
>>>
>>> usr/Makefile:64: *** multiple target patterns. Stop.
>> [...]
>>> Which sorts of make sense here because the file name contains a ":"
>>> which is not escaped, so GNU Make tries to interpret it.
>>>
>>> Now the part that does not quite make sense to me is why this file is
>>> even relevant here considering that the first thing we do is set
>>> CONFIG_INITRAMFS_SOURCE="" to disable the initramfs basically.
>>
>> It is possible that we read usr/Makefile twice for some reason. But the
>> real problem is the lack of escaping. Can you try the following
>> (untested) patch?
>
> Can you submit an official patch for this? Thanks a lot!
The % escape is wrong. I'm trying to fix it or drop this escape.
Michal
next prev parent reply other threads:[~2016-09-23 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 0:12 Florian Fainelli
2016-09-13 7:24 ` Michal Marek
2016-09-13 17:28 ` Florian Fainelli
2016-09-19 20:00 ` Florian Fainelli
2016-09-23 7:05 ` Michal Marek [this message]
2016-09-23 8:35 ` [PATCH] initramfs: Escape colons in depfile Michal Marek
2016-10-27 10:35 ` [LEDE-DEV] " John Crispin
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=ef840fed-065a-7b03-580e-66add0d89f59@suse.com \
--to=mmarek@suse.com \
--cc=f.fainelli@gmail.com \
--cc=joe@perches.com \
--cc=lede-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=openwrt-devel@lists.openwrt.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®