All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>,
	jirislaby@gmail.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jeff Mahoney <jeffm@suse.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-usb@vger.kernel.org,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	linux-geode@lists.infradead.org, linux-fbdev@vger.kernel.org,
	Richard Cochran <richardcochran@gmail.com>,
	netdev@vger.kernel.org, "Keller,
	Jacob E" <jacob.e.keller@intel.com>
Subject: Re: [PATCH] build some drivers only when compile-testing
Date: Fri, 24 May 2013 04:50:30 +0000	[thread overview]
Message-ID: <1369371030.2776.17@driftwood> (raw)
In-Reply-To: <1369317700.3469.256.camel@deadeye.wl.decadent.org.uk> (from ben@decadent.org.uk on Thu May 23 09:01:40 2013)
In-Reply-To: <20130523022327.GB6159@kroah.com>

On 05/23/2013 09:01:40 AM, Ben Hutchings wrote:
> On Wed, 2013-05-22 at 19:23 -0700, Greg Kroah-Hartman wrote:
> > On Wed, May 22, 2013 at 11:18:46AM +0200, Jiri Slaby wrote:
> > > Some drivers can be built on more platforms than they run on. This
> > > causes users and distributors packaging burden when they have to
> > > manually deselect some drivers from their allmodconfigs. Or  
> sometimes
> > > it is even impossible to disable the drivers without patching the
> > > kernel.
> > >
> > > Introduce a new config option COMPILE_TEST and make all those  
> drivers
> > > to depend on the platform they run on, or on the COMPILE_TEST  
> option.
> > > Now, when users/distributors choose COMPILE_TEST=n they will not  
> have
> > > the drivers in their allmodconfig setups, but developers still can
> > > compile-test them with COMPILE_TEST=y.
> >
> > I understand the urge, and it's getting hard for distros to handle  
> these
> > drivers that just don't work on other architectures, but it's really
> > valuable to ensure that they build properly, for those of us that  
> don't
> > have many/any cross compilers set up.

In http://landley.net/aboriginal/bin grab the cross-compiler-*.tar.bz2  
tarballs, extract them, add the "bin" subdirectory of each to the  
$PATH. Congratulations, you have cross compilers set up. (They're  
statically linked and relocatable, so should run just about anywhere.  
If they don't, let me know and I'll fix it.)

Example build:

   make ARCH=sparc sparc32_defconfig
   PATH=/home/landley/simple-cross-compiler-sparc/bin:$PATH \
     make ARCH=sparc CROSS_COMPILE=sparc-

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>,
	jirislaby@gmail.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jeff Mahoney <jeffm@suse.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-usb@vger.kernel.org,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
	linux-geode@lists.infradead.org, linux-fbdev@vger.kernel.org,
	Richard Cochran <richardcochran@gmail.com>,
	netdev@vger.kernel.org, "Keller,
	Jacob E" <jacob.e.keller@intel.com>
Subject: Re: [PATCH] build some drivers only when compile-testing
Date: Thu, 23 May 2013 23:50:30 -0500	[thread overview]
Message-ID: <1369371030.2776.17@driftwood> (raw)
In-Reply-To: <1369317700.3469.256.camel@deadeye.wl.decadent.org.uk> (from ben@decadent.org.uk on Thu May 23 09:01:40 2013)

On 05/23/2013 09:01:40 AM, Ben Hutchings wrote:
> On Wed, 2013-05-22 at 19:23 -0700, Greg Kroah-Hartman wrote:
> > On Wed, May 22, 2013 at 11:18:46AM +0200, Jiri Slaby wrote:
> > > Some drivers can be built on more platforms than they run on. This
> > > causes users and distributors packaging burden when they have to
> > > manually deselect some drivers from their allmodconfigs. Or  
> sometimes
> > > it is even impossible to disable the drivers without patching the
> > > kernel.
> > >
> > > Introduce a new config option COMPILE_TEST and make all those  
> drivers
> > > to depend on the platform they run on, or on the COMPILE_TEST  
> option.
> > > Now, when users/distributors choose COMPILE_TEST=n they will not  
> have
> > > the drivers in their allmodconfig setups, but developers still can
> > > compile-test them with COMPILE_TEST=y.
> >
> > I understand the urge, and it's getting hard for distros to handle  
> these
> > drivers that just don't work on other architectures, but it's really
> > valuable to ensure that they build properly, for those of us that  
> don't
> > have many/any cross compilers set up.

In http://landley.net/aboriginal/bin grab the cross-compiler-*.tar.bz2  
tarballs, extract them, add the "bin" subdirectory of each to the  
$PATH. Congratulations, you have cross compilers set up. (They're  
statically linked and relocatable, so should run just about anywhere.  
If they don't, let me know and I'll fix it.)

Example build:

   make ARCH=sparc sparc32_defconfig
   PATH=/home/landley/simple-cross-compiler-sparc/bin:$PATH \
     make ARCH=sparc CROSS_COMPILE=sparc-

Rob

  parent reply	other threads:[~2013-05-24  4:50 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  9:18 [PATCH] build some drivers only when compile-testing Jiri Slaby
2013-05-23  2:23 ` Greg Kroah-Hartman
2013-05-23  2:23   ` Greg Kroah-Hartman
2013-05-23  3:09   ` Jeff Mahoney
2013-05-23  3:09     ` Jeff Mahoney
2013-05-23  3:09     ` Jeff Mahoney
2013-06-17 20:05     ` Jiri Slaby
2013-06-17 20:05       ` Jiri Slaby
2013-06-18  4:51       ` Michal Marek
2013-06-18  4:51         ` Michal Marek
2013-06-18  8:18         ` Felipe Balbi
2013-06-18  8:18           ` Felipe Balbi
2013-06-18  8:24           ` Jiri Slaby
2013-06-18  8:24             ` Jiri Slaby
2013-06-18  8:34             ` Felipe Balbi
2013-06-18  8:34               ` Felipe Balbi
2013-06-18  8:34               ` Felipe Balbi
2013-06-18  8:44               ` Michal Marek
2013-06-18  8:44                 ` Michal Marek
2013-06-18  8:51                 ` Felipe Balbi
2013-06-18  8:51                   ` Felipe Balbi
2013-06-18  8:51                   ` Felipe Balbi
2013-06-18  9:21                   ` Jiri Slaby
2013-06-18  9:21                     ` Jiri Slaby
2013-06-19 16:38               ` Mark Brown
2013-06-19 16:38                 ` Mark Brown
2013-06-18  8:35         ` Tomi Valkeinen
2013-06-18  8:35           ` Tomi Valkeinen
2013-06-18 16:04       ` Greg Kroah-Hartman
2013-06-18 16:04         ` Greg Kroah-Hartman
2013-06-19  6:50         ` Jiri Slaby
2013-06-19  6:50           ` Jiri Slaby
2013-06-19  6:50           ` Jiri Slaby
2013-06-24 23:42           ` Greg Kroah-Hartman
2013-06-24 23:42             ` Greg Kroah-Hartman
2013-06-25  8:16             ` Jiri Slaby
2013-06-25  8:16               ` Jiri Slaby
2013-06-19  7:10       ` Tomi Valkeinen
2013-06-19  7:10         ` Tomi Valkeinen
2013-06-19  7:12         ` Jiri Slaby
2013-06-19  7:12           ` Jiri Slaby
2013-06-19  7:19           ` Tomi Valkeinen
2013-06-19  7:19             ` Tomi Valkeinen
2013-06-19 14:27           ` Greg Kroah-Hartman
2013-06-19 14:27             ` Greg Kroah-Hartman
2013-06-19 14:27             ` Greg Kroah-Hartman
2013-06-21 11:11             ` [PATCH v3] " Jiri Slaby
2013-05-23 14:01   ` [PATCH] " Ben Hutchings
2013-05-23 14:01     ` Ben Hutchings
2013-05-23 14:01     ` Ben Hutchings
2013-05-24  4:50   ` Rob Landley [this message]
2013-05-24  4:50     ` Rob Landley
2013-05-23  7:46 ` Tomi Valkeinen
2013-05-23  7:46   ` Tomi Valkeinen

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=1369371030.2776.17@driftwood \
    --to=rob@landley.net \
    --cc=FlorianSchandinat@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jeffm@suse.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=torvalds@linux-foundation.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.