public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Espen Carlsen" <ec@numascale.com>
To: "'Paul Bolle'" <pebolle@tiscali.nl>
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, 8 Jul 2015 20:47:12 +0200	[thread overview]
Message-ID: <010a01d0b9ae$809dd5e0$81d981a0$@numascale.com> (raw)
In-Reply-To: <1436372280.20619.24.camel@tiscali.nl>

> From: Paul Bolle [mailto:pebolle@tiscali.nl]
> On wo, 2015-07-08 at 17:42 +0200, Espen Carlsen wrote:
> Wild guess: do the Ubuntu systems already have
>     /lib/modules/4.1.0/build
>     /lib/modules/4.1.0/source
> as symlinks to /usr/src/kernels/4.1.0 when you're building the rpms?
> (That is, not in rpm's buildroot, but in the actual filesystem.)

No, I don't have any 4.x kernels installed on that system, just 3.16 Ubuntu kernel.
I assume your wild guess was that if I had /lib/modules/4.1.0/build & source as that was the kernel I was building?

Also, so you know, the issue isn't related to the 4.1.0 kernel, I can reproduce this on 4.0.x, 3.19.x and 3.18.x.
Probably others also, but those are the ones I've tried.
On all of them when I compile on Ubuntu, there will be a build and source softlink in the lib/modules/version/ directory
of BUILDROOT.

Espen


  reply	other threads:[~2015-07-08 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 11:47 [PATCH, resend] build: fix broken kernel RPM source symlink 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 [this message]
2015-07-08 18:52             ` Paul Bolle
2015-07-08 16:56     ` Paul Bolle
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='010a01d0b9ae$809dd5e0$81d981a0$@numascale.com' \
    --to=ec@numascale.com \
    --cc=daniel@numascale.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=pebolle@tiscali.nl \
    --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