linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Barry <bobb@absamail.co.za>
To: linux-hotplug@vger.kernel.org
Subject: Re: latest klibc for udev
Date: Fri, 24 Sep 2004 12:48:09 +0000	[thread overview]
Message-ID: <200409220810.08974.bobb@absamail.co.za> (raw)
In-Reply-To: <20040917191134.GA28506@vrfy.org>

Kevin & Kay-

On Mon, 20 Sep 2004 07:51 Kevin wrote:
> ...you said that the udev package needs to "provide klibc-0.17x" the 
> support the 2.6.9-rc2 kernel, and I was disagreeing. That should only be 
> necessary if you are allowing udev/klibc to build against raw kernel 
> headers, instead of sanitized headers. I run udev-032 against 2.6.9-rc2 
> kernels here and have not had any trouble.
I got the latest linux-libc-headers and installed them, and upgraded
my glibc from 2.3.2 to 2.3.3, but compilation of klibc still failed under
linux-2.6.9-rc2.  The failure was always in compilation of ash (which
I didn't really want anyway).  I finally found that ash requires a recent
version of bison; version 1.35 failed, but 1.75 succeeds.  Makefile in
klibc root directory should test for bison version.

Does udev use ash?  Might it be used in future?  The udev build would be quicker,
and independent of yacc and bison, if ash were not built.

The following script, in same directory as Kay's patches, builds udev
with recent klibc:
  #!/bin/ksh
  rm -rf udev-032
  tar xjvf /usr/portage/distfiles/udev-032.tar.bz2
  cd udev-032
  tar xjvf /usr/portage/distfiles/klibc-0.179.tar.bz2
  mv klibc-0.179 klibc
  patch -p1 < ../udev-klibc-last-01.patch
  patch -p0 < ../klibc-bug-01.patch
  ln -s /usr/src/linux-2.6.9-rc2 klibc/linux
  make KERNEL_DIR=/usr/src/linux-2.6.9-rc2 USE_KLIBC=true USE_LOGúlse DEBUGúlse

If line "ln -s /usr/src/linux-2.6.9-rc2 klibc/linux" is omitted, script fails despite
KERNEL_DIR parameter in make command.

Running
  make KERNEL_DIR=/usr/src/linux-2.6.9-rc2 USE_KLIBC=true USE_LOGúlse DEBUGúlse
on unpatched udev-032 fails every time.
Running
  make KERNEL_DIR=/usr/src/linux-2.6.9-rc1 USE_KLIBC=true USE_LOGúlse DEBUGúlse
on unpatched udev-032 succeeds.

Thanks,

Bob Barry


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-09-24 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 19:11 latest klibc for udev Kay Sievers
2004-09-18  0:31 ` [klibc] " H. Peter Anvin
2004-09-18 21:44 ` Bob Barry
2004-09-19 20:18 ` Kevin P. Fleming
2004-09-20  7:23 ` Bob Barry
2004-09-20 14:51 ` Kevin P. Fleming
2004-09-24 12:48 ` Bob Barry [this message]
2004-09-29 14:31 ` [klibc] " Jürg Billeter
2004-09-29 18:25 ` H. Peter Anvin

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=200409220810.08974.bobb@absamail.co.za \
    --to=bobb@absamail.co.za \
    --cc=linux-hotplug@vger.kernel.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 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).