linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Olaf Hering <olh@suse.de>
Cc: Stefan Jeglinski <jeglin@4pi.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6 hoses 2.4 on old-world?
Date: Sun, 22 Aug 2004 10:57:09 +0200	[thread overview]
Message-ID: <20040822085709.GA7319@mars.ravnborg.org> (raw)
In-Reply-To: <20040821225118.GB18858@suse.de>


On Sun, Aug 22, 2004 at 12:51:18AM +0200, Olaf Hering wrote:
>
>  On Fri, Aug 20, Stefan Jeglinski wrote:
>
> >
> > >Steps:
> > >
> > >make menuconfig
> > >(do some config)
> > >make
> > >make modules_install
> > >reboot
> >
> > Confirmed. Something about this procedure with 2.6.8-rc4 is hosing
> > /dev/null, and I have to delete it and mknod again. Is this a known
> > bug, or have I discovered something that everybody's known about
> > forever, and I should slink away. Or maybe I don't understand how to
> > build/install 2.6 correctly?
>
> for starters:
>
> useradd -m jeglin
> su - jeglin
> tar xfj linux-2.6.8.1.tar.bz2
> cd linux-2.6.8.1
> make menuconfig
> make all
> cd ~jeglin/linux-2.6.8.1
> make modules_install
sudo make modules_install
> reboot
>
> the binutils check (?) will remove /dev/null

Yep - Tom Rini already notified me about this issue.
Problem is the way as handle output files.

Now I wonder why I do not see the problem here when executing the
culprint part of arch/ppc/Makefile manually:

sam@mars kbuild $ sudo ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 Jun 15 23:54 /dev/null
sam@mars kbuild $ sudo echo dssall | as -many -o /dev/null >/dev/null 2>&1
sam@mars kbuild $ sudo ls -l /dev/null
crw-rw-rw-  1 root root 1, 3 Jun 15 23:54 /dev/null

Tom asked if we could use mktemp in the build process,
but I really do not know enough about potential security issues
to start doing this.
With mktemp we could avoid using /dev/null in the as check.

Another possibility was to parse the output of:
as --version | head -n 1 | cut -d ' ' -f 3
And then some sed/awk magic to fetch the three first numbers and
always make then two digits wide: 2.14.90.0.8 => 021490

	Sam

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-22  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21  1:04 2.6 hoses 2.4 on old-world? Stefan Jeglinski
2004-08-21  1:41 ` CaT
2004-08-21  2:05 ` Stefan Jeglinski
2004-08-21  2:18   ` Stefan Jeglinski
2004-08-21 22:51     ` Olaf Hering
2004-08-22  8:57       ` Sam Ravnborg [this message]
2004-08-23  0:54       ` Stefan Jeglinski

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=20040822085709.GA7319@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=jeglin@4pi.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).