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: udev's klibc and kernel 2.6.9-rc2
Date: Fri, 17 Sep 2004 10:12:28 +0000	[thread overview]
Message-ID: <200409171212.28255.bobb@absamail.co.za> (raw)

While making an initrd for kernel 2.6.9-rc2, I found that udev's klibc did not compile.
Attempted compilation of udev-032 with command line:
	make clean; make USE_KLIBC=true USE_LOGúlse DEBUGúlse
ends with:
	make[2]: *** [inet/inet_ntoa.o] Error 1
	make[2]: Leaving directory `/home/bobb/udev/udev-032/klibc/klibc'
	make[1]: *** [all] Error 2
	make[1]: Leaving directory `/home/bobb/udev/udev-032/klibc'
	make: *** [/home/bobb/udev/udev-032/klibc/klibc/crt0.o] Error 2

I got klibc-0.157.tar.bz2 (stable) and klibc-0.178.tar.bz2 (not stable) to see if they would compile.
Klibc-0.157 fails with:
	make: *** [inet/inet_ntoa.o] Error 1
Klibc-0.178 compiles successfully.

I'm using gcc-3.2.3. Compilation of udev for initrd of previous kernels had no problem.

Suggestions?  Is klibc-0.178 compatible with udev?

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

             reply	other threads:[~2004-09-17 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 10:12 Bob Barry [this message]
2004-09-17 15:09 ` udev's klibc and kernel 2.6.9-rc2 Kay Sievers

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=200409171212.28255.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).