From: Paul Bolle <pebolle@tiscali.nl>
To: Espen Carlsen <ec@numascale.com>
Cc: "'Michal Marek'" <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Daniel J Blueman'" <daniel@numascale.com>,
"'Steffen Persvold'" <sp@numascale.com>
Subject: Re: [PATCH, resend] build: fix broken kernel RPM source symlink
Date: Wed, 08 Jul 2015 18:56:22 +0200 [thread overview]
Message-ID: <1436374582.20619.40.camel@tiscali.nl> (raw)
In-Reply-To: <006601d0b823$2b144820$813cd860$@numascale.com>
[I resisted looking into the flood of info you included in this message.
But this part could turn out to be interesting.]
On ma, 2015-07-06 at 21:37 +0200, Espen Carlsen wrote:
> This is the how BUILDROOT looks after rpmbuild -bi kernel-4.1.0.spec
> on an Ubuntu system, notice that on Ubuntu, there are already a
> 'build' and 'source' symlink before the ln -sf commands are issued,
> CentOS however doesn't have those links on the same step.
> user@build-ubuntu:/srv/user/rpmbuild$ rpmbuild -bi SPECS/kernel-4.1.0.spec
That is outside the realm of "make rpm".
I assume kernel-4.1.0.spec was a copy, somehow made, of kernel.spec as
was created by "make rpm". Does it matter, for the issue you ran into,
whether "make rpm" or "rpmbuild -bb SPECS/kernel.spec" is involved?
> user@build-ubuntu:/srv/user/rpmbuild/BUILDROOT/kernel-4.1.0-1.x86_64/lib/modules/4.1.0$ ls -gG
> total 64
> lrwxrwxrwx 1 35 Jul 6 18:56 build -> /srv/user/rpmbuild/BUILD/kernel-4.1.0
> [...]
> lrwxrwxrwx 1 35 Jul 6 19:00 source -> /srv/user/rpmbuild/BUILD/kernel-4.1.0
These two links are, I think, generated in this snippet from the main
Makefile:
_modinst_:
@rm -rf $(MODLIB)/kernel
@rm -f $(MODLIB)/source
@mkdir -p $(MODLIB)/kernel
@ln -s `cd $(srctree) && /bin/pwd` $(MODLIB)/source
@if [ ! $(objtree) -ef $(MODLIB)/build ]; then \
rm -f $(MODLIB)/build ; \
ln -s $(CURDIR) $(MODLIB)/build ; \
fi
@cp -f $(objtree)/modules.order $(MODLIB)/
@cp -f $(objtree)/modules.builtin $(MODLIB)/
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modinst
I wonder why you don't see similar links when building on CentOS. I saw
similar links in rpm's BUILDROOT when building on Fedora 22.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-07-08 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 11:47 Espen Carlsen
2015-07-04 10:19 ` Paul Bolle
2015-07-06 19:37 ` Espen Carlsen
2015-07-08 14:26 ` Paul Bolle
2015-07-08 15:42 ` Espen Carlsen
2015-07-08 16:18 ` Paul Bolle
2015-07-08 18:47 ` Espen Carlsen
2015-07-08 18:52 ` Paul Bolle
2015-07-08 16:56 ` Paul Bolle [this message]
2015-07-09 9:29 ` Espen Carlsen
2015-08-19 15:14 ` Michal Marek
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=1436374582.20619.40.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=daniel@numascale.com \
--cc=ec@numascale.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sp@numascale.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
Powered by JetHome