dump latest klibc into the udev build tree
PATCH 1/1 dump latest klibc into the udev build tree
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.
Makefile +6 -6
@@ -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)
README +3 -3
@@ -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:
Signature · 14 lines
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_id78&alloc_id371&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 3 lines · Olaf Hering
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.
Why is this needed? I don't see the KLIBC variable needed in the latest cvs tree of klibc.
thanks,
greg k-h
-------------------------------------------------------
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_id78&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 3 lines · Olaf Hering
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.
Why is this needed? I don't see the KLIBC variable needed in the latest cvs tree of klibc.
thanks,
greg k-h
-------------------------------------------------------
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_id78&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 7 lines · Greg KH
Quoted 3 lines · Olaf Hering
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.
Why is this needed? I don't see the KLIBC variable needed in the latest cvs tree of klibc.
KLIBC holds libc.a
grep -wr KLIBC /trashcan/olaf/klibc/klibc-0.94/
/trashcan/olaf/klibc/klibc-0.94/ash/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/MCONFIG:KLIBC = $(KLIBSRC)/libc.a
/trashcan/olaf/klibc/klibc-0.94/gzip/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/ipconfig/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/kinit/Makefile: $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/nfsmount/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/utils/Makefile:LIBS = $(KLIBC) $(LIBGCC)
Signature · 14 lines
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_id78&alloc_id371&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 12 lines · Olaf Hering
Quoted 7 lines · Greg KH
Quoted 3 lines · Olaf Hering
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.
Why is this needed? I don't see the KLIBC variable needed in the latest cvs tree of klibc.
KLIBC holds libc.a
Quoted 8 lines
grep -wr KLIBC /trashcan/olaf/klibc/klibc-0.94/
/trashcan/olaf/klibc/klibc-0.94/ash/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/MCONFIG:KLIBC = $(KLIBSRC)/libc.a
/trashcan/olaf/klibc/klibc-0.94/gzip/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/ipconfig/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/kinit/Makefile: $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/nfsmount/Makefile:LIBS = $(KLIBC) $(LIBGCC)
/trashcan/olaf/klibc/klibc-0.94/utils/Makefile:LIBS = $(KLIBC) $(LIBGCC)
But the udev build does not contain any of those "addons" in it's version of the klibc tree, right? So why would it matter to udev?
thanks,
greg k-h
-------------------------------------------------------
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_id78&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 2 lines · Greg KH
But the udev build does not contain any of those "addons" in it's version of the klibc tree, right? So why would it matter to udev?
Thats the reason why the subject line reads: dump the latest and greatest ...
like that:
rm -rf klibc/* ; cp -a klibc-0.94/* klibc
make KLIBC=true -j || echo patch missing
I build udev and klibc stuff in one go.
Signature · 14 lines
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_id78&alloc_id371&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 5 lines · Olaf Hering
Quoted 2 lines · Greg KH
But the udev build does not contain any of those "addons" in it's version of the klibc tree, right? So why would it matter to udev?
Quoted 7 lines
Thats the reason why the subject line reads: dump the latest and greatest ...
like that:
rm -rf klibc/* ; cp -a klibc-0.94/* klibc
make KLIBC=true -j || echo patch missingI build udev and klibc stuff in one go.
Ah, ok, that makes sense. I've now applied your patch, thanks.
greg k-h
-------------------------------------------------------
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_id78&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel