From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] dump latest klibc into the udev build tree
Date: Tue, 16 Dec 2003 08:22:42 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107156299722581@msgid-missing> (raw)
KLIBC is used as an internal makefile variable, it expands to either
true or false right now. udev should use something else than KLIBC to
allow build against the latest and greatest klibc version.
diff -p -purN udev.bk/Makefile udev.bk.new/Makefile
--- udev.bk/Makefile 2003-12-11 09:12:28.000000000 +0100
+++ udev.bk.new/Makefile 2003-12-13 09:28:26.000000000 +0100
@@ -22,7 +22,7 @@ DEBUG = false
# Set the following to `true' to make udev emit a D-BUS signal when a
# new node is created.
-DBUS = false
+USE_DBUS = false
ROOT = udev
@@ -56,7 +56,7 @@ udevdir = ${prefix}/udev
# Comment out this line to build with something other
# than the local version of klibc
-#KLIBC = true
+#USE_KLIBC = true
# If you are running a cross compiler, you may want to set this
# to something more interesting, like "arm-linux-". I you want
@@ -115,7 +115,7 @@ endif
# If we are using our version of klibc, then we need to build and link it.
# Otherwise, use glibc and link statically.
-ifeq ($(strip $(KLIBC)),true)
+ifeq ($(strip $(USE_KLIBC)),true)
KLIBC_BASE = $(PWD)/klibc
KLIBC_DIR = $(KLIBC_BASE)/klibc
INCLUDE_DIR := $(KLIBC_DIR)/include
@@ -179,11 +179,11 @@ OBJS = udev.o \
$(SYSFS) \
$(TDB)
-ifeq ($(strip $(KLIBC)),true)
+ifeq ($(strip $(USE_KLIBC)),true)
OBJS += klibc_fixups.o
endif
-ifeq ($(DBUS), true)
+ifeq ($(USE_DBUS), true)
CFLAGS += -DUSE_DBUS
CFLAGS += $(shell pkg-config --cflags dbus-1)
LDFLAGS += $(shell pkg-config --libs dbus-1)
@@ -260,7 +260,7 @@ small_release: $(DISTFILES) clean
@echo "Built $(RELEASE_NAME).tar.gz"
-ifeq ($(DBUS), true)
+ifeq ($(USE_DBUS), true)
install-dbus-policy:
$(INSTALL) -d $(DESTDIR)$(dbusdir)
$(INSTALL_DATA) udev_sysbus_policy.conf $(DESTDIR)$(dbusdir)
diff -p -purN udev.bk/README udev.bk.new/README
--- udev.bk/README 2003-12-08 19:08:52.000000000 +0100
+++ udev.bk.new/README 2003-12-13 09:28:58.000000000 +0100
@@ -32,18 +32,18 @@ To use:
installed into. This works just like the 'configure --prefix'
script does. Default value is ''. Only override this if you
really know what you are doing.
- KLIBC - if set to 'true', udev is built and linked against the included
+ USE_KLIBC - if set to 'true', udev is built and linked against the included
version of klibc. Default value is 'false'.
DEBUG - if set to 'true', debugging messages will be sent to the syslog
as udev is run. Default value is 'false'.
- DBUS - if set to 'true', DBUS messages will be sent everytime udev
+ USE_DBUS - if set to 'true', DBUS messages will be sent everytime udev
creates or removes a device node. This requires that DBUS
development headers and libraries be present on your system to
build properly. Default value is 'false'.
So, if you want to build udev using klibc with debugging messages, you
would do:
- make KLIBC=true DEBUG=true
+ make USE_KLIBC=true DEBUG=true
- Install the project:
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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
next reply other threads:[~2003-12-16 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 8:22 Olaf Hering [this message]
2003-12-16 8:34 ` [PATCH] dump latest klibc into the udev build tree Greg KH
2003-12-16 15:28 ` Greg KH
2003-12-16 16:33 ` Olaf Hering
2003-12-16 16:58 ` Greg KH
2003-12-16 18:36 ` Olaf Hering
2003-12-16 23:46 ` Greg KH
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=marc-linux-hotplug-107156299722581@msgid-missing \
--to=olh@suse.de \
--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).