mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg KH <greg@kroah.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] Kernel version numbering scheme change
Date: Sat, 18 Oct 2008 16:48:33 +0300	[thread overview]
Message-ID: <20081018134832.GC6535@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081018122851.GB25503@1wt.eu>

On Sat, Oct 18, 2008 at 02:28:51PM +0200, Willy Tarreau wrote:
> On Sat, Oct 18, 2008 at 02:50:38PM +0300, Adrian Bunk wrote:
>...
> > > > Scratchbox [1], e.g. used for building the software in Nokias Internet 
> > > > Tablets [2] or the ARM Linux Internet Platform [3], is a chrooted 
> > > > cross-compilation environment.
> > > > 
> > > > Yes, it works.
> > > 
> > > I'm not saying it does not work, I'm saying it's far from being practical
> > > when you want to support multiple architectures or targets, and that it
> > > will do nasty things under you without letting you know.
> > 
> > Scratchbox easily allows switching between targets, no matter which 
> > architectures they are for.
> > 
> > Can you describe the problems you have experienced more precisely?
> 
> Adrian, don't try to make me look like dumb by asking for specific
> problems. Problems range from auto-detection of kernel version to

> enable or disable feature X or Y,

Works inside Scratchbox.

> to endian detection and bit width

Works inside Scratchbox.

> detection. If you don't believe me, it's just that you're used to
> build completely OS-agnostic packages,

That's completely wrong.

> which is perfectly fine, but
> that doesn't seem to be completely the case given that you're feeling
> you will get annoyed by breaking the openssl BUILD environment if
> you make it run on a different kernel. *That* is the funny part,
> since this build environment should not even require to run on Linux
> at all!

10 years ago someone wrote his own version of config.guess, and assumed 
kernel developers would always use sane versions.

This doesn't make it Linux-specific.

>...
> > > A build environment is what it is, a build environment. It contains
> > > compilers, shells to run scripts, various interpreters and build tools,
> > > possibily debuggers and editors, versionning systems, etc...
> > 
> > The build environment in the chroot is the correct release.    
> 
> No it isn't because you're saying that some of the packages check for
> kernel version which is not the right one. So if you move your chroot
> to another machine, it is susceptible to break because it relies on
> the host's kernel version. So your chroot is not your build environment,
> it's just part of it.

The version is one of the few things the kernel leaks inside a chroot.

> > > > Userspace ABIs of the kernel are usually stable.
> > > 
> > > Yes but they are not necessarily forward-compatible. If openssl believes
> > > some feature is present in 2.6.521 because 521 is bigger than 233, you
> > > will build a broken package which will not work with any distro running
> > > your long-term 2.6.27 which does not have the feature introduced in .233.
> > 
> > I already addressed this previously in this thread:
> > 
> > I'm not even sure whether OpenSSL actually does anything with the 
> > information: The script comes from the Apache foundation and
> > claims to be "Similar to config.guess but much, much smaller."
> 
> You addressed it only for openssl and apache 1.3, that you used as
> examples to object to a change of changing kernel version numbering
> scheme. So do you have other examples of packages like this which
> might break and might be more sensible to build environment's kernel
> version ? Because if only apache 1.3 and openssl 0.9.8g are sensible,
> the fix will be really quick using something like this in your build
> scripts and makefiles :
>...
> And BTW, if your build environment mimmics so well the target except
> for uname, let's fix its uname tool to reflect the target version !

The problem has nothing to do with any build environments or chroots.

A "just for fun" change of the version number will break existing 
programs, and that will cause various problems for various people.

> > > And when
> > > you know how to fix packages so that chroot is not a problem, then you
> > > know how to fix the package not to require a chroot.
> > 
> > That's complete bullshit:
> > 
> > Packages do not require fixes for being built inside a chroot.
> > 
> > Given:
> > - some software package of a foobar program
> > - Scratchbox on an x86 host
> > - an ARM target that mounts the target filesystem from the host
> > 
> > host   # ./configure && make && make install
> > target # foobar
> > 
> > The build system of the software thinks it gets built on the target 
> > architecture.
> 
> Quite cool stuff, but I'm really not interested. Having been beat by
> a number of packages which try to run target environment commands
> during the build when not set for cross-compile, I'd expect pretty
> random results.

The build system of the package thinks it gets compiled natively - that 
avoids exactly the problems you describe.

And trying to run a target binary when building on the host *does work* 
inside Scratchbox. Please *read* what I wrote directly below:

> > And due to transparent usage of qemu or sbrsh it also works when the 
> > package uses a program built for the target during the build.
> > No matter whether the build system of the package knows anything about
> > cross-compilation.
>...
> Willy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-10-18 13:49 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  0:25 Greg KH
2008-10-16  1:03 ` H. Peter Anvin
2008-10-16  1:51   ` David Sanders
2008-10-16  2:18   ` Greg KH
2008-10-16  7:02 ` Thorsten Leemhuis
2008-10-16  7:34   ` david
2008-10-18 21:44     ` Jan Engelhardt
2008-10-19  1:52       ` david
2008-10-19  2:44         ` Jan Engelhardt
2008-10-16  8:21 ` el es
2008-10-16  9:09   ` H. Peter Anvin
2008-10-16  9:33     ` el es
2008-10-16 10:05       ` el es
2008-10-16 10:14         ` Kristoffer Ericson
2008-10-16 17:30       ` david
2008-10-16  9:15 ` Hans J. Koch
2008-10-16 15:21   ` Geert Uytterhoeven
2008-10-18 21:56   ` Jan Engelhardt
2008-10-16 12:49 ` Adrian Bunk
2008-10-16 15:17   ` Greg KH
2008-10-16 15:30     ` Bill Nottingham
2008-10-16 15:47       ` Greg KH
2008-10-16 17:16         ` Adrian Bunk
2008-10-17  4:02           ` Greg KH
2008-10-17  4:26             ` Grant Coady
2008-10-17  4:53             ` Randy Dunlap
2008-10-17  9:31             ` Alan Cox
2008-10-17 16:40               ` H. Peter Anvin
2008-10-17 17:42                 ` Greg KH
2008-10-18  7:18                   ` H. Peter Anvin
2008-10-18  7:38                     ` 2.6.28-rc1 --> 2.8.0-rc1; 2.6.27.y --> 2.6.28 [Re: [RFC] Kernel version numbering scheme change] Dominik Brodowski
2008-10-18  7:47                       ` Mikael Abrahamsson
2008-10-20  3:48                     ` [RFC] Kernel version numbering scheme change Alexandre Oliva
2008-10-20  5:29                       ` H. Peter Anvin
2008-10-20  7:13                         ` Alexandre Oliva
2008-10-20 18:55                       ` Alex Howells
2008-10-20 20:21                         ` Greg KH
2008-10-21 19:52                           ` Alex Howells
2008-10-22  0:41                             ` Valdis.Kletnieks
2008-10-22  4:15                               ` Grant Coady
2008-10-22  8:58                               ` Alex Howells
2008-10-22  9:11                                 ` Alan Cox
2008-10-22 18:11                             ` Stefan Richter
2008-10-21 18:54                         ` Stefan Richter
2008-10-17 17:41               ` Greg KH
2008-10-17 19:45                 ` Alan Cox
2008-10-17 21:42                   ` Greg KH
2008-10-16 16:46     ` Adrian Bunk
2008-10-17  3:47       ` Greg KH
2008-10-17  6:47         ` Adrian Bunk
2008-10-17  7:55           ` Greg KH
2008-10-17  8:16             ` Steven Noonan
2008-10-17 17:46               ` Greg KH
2008-10-17 19:06                 ` Bartlomiej Zolnierkiewicz
2008-10-17 21:44                   ` Greg KH
2008-10-17 19:47                 ` Alan Cox
2008-10-17 21:44                   ` Greg KH
2008-10-17 22:14                     ` Matthias Schniedermeyer
2008-10-17 22:49                     ` Rafael J. Wysocki
2008-10-18  1:23                       ` david
2008-10-18 23:14                         ` Jiri Kosina
2008-10-19  1:50                           ` david
2008-10-19 12:51                           ` Rafael J. Wysocki
2008-10-19 16:29                             ` david
2008-10-19 17:45                               ` Rafael J. Wysocki
2008-10-19 17:47                                 ` david
2008-10-19 17:57                                   ` Rafael J. Wysocki
2008-10-18  8:45                     ` Willy Tarreau
2008-10-18 23:17                       ` Jiri Kosina
2008-10-19  3:35                         ` Willy Tarreau
2008-10-20 20:30                       ` Greg KH
2008-10-20 20:54                         ` Felipe Balbi
2008-10-20 21:06                           ` Greg KH
2008-10-20 21:58                             ` Arnd Bergmann
2008-10-20 22:24                             ` Felipe Balbi
2008-10-21 19:11                               ` Stefan Richter
2008-10-21 19:16                                 ` Felipe Balbi
2008-10-18 22:33                     ` Jan Engelhardt
2008-10-19 18:33                       ` Greg KH
2008-10-19 19:51                         ` Jan Engelhardt
2008-10-19 23:40                           ` david
2008-10-18 22:38                     ` Jan Engelhardt
2008-10-18  1:20               ` david
2008-10-18  8:32               ` Willy Tarreau
2008-10-17  8:56             ` Adrian Bunk
2008-10-17 10:06               ` Peter Zijlstra
2008-10-17 11:18                 ` Alexey Dobriyan
2008-10-17 11:26                   ` Peter Zijlstra
2008-10-17 11:32                     ` Alexey Dobriyan
2008-10-17 15:30               ` Chris Friesen
2008-10-17 17:45               ` Greg KH
2008-10-18  9:01               ` Willy Tarreau
2008-10-18 10:04                 ` Adrian Bunk
2008-10-18 11:08                   ` Willy Tarreau
2008-10-18 11:50                     ` Adrian Bunk
2008-10-18 12:28                       ` Willy Tarreau
2008-10-18 13:48                         ` Adrian Bunk [this message]
2008-10-18 14:13                           ` Willy Tarreau
2008-10-16 14:26 ` markus reichelt
2008-10-16 15:35   ` Theodore Tso
2008-10-16 18:05     ` John Stoffel
2008-10-16 19:14     ` Harald Arnesen
2008-10-17  1:53     ` Dave Young
2008-10-17  9:05       ` Jike Song
2008-10-17  9:14         ` Dave Young
2008-10-20  3:49     ` Daniel Phillips
2008-10-16 15:18 ` Geert Uytterhoeven
2008-10-17  1:26 ` Rob Landley
2008-10-17 12:46 ` Giacomo A. Catenazzi
2008-10-17 17:40   ` Greg KH
2008-10-18  1:32   ` david
2008-10-16  2:10 H. Peter Anvin
2008-10-20  6:05 Denys Fedoryshchenko

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=20081018134832.GC6535@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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®