From: WebmasterMattD <webmattd@webmastermattd.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] couple of newbie questions.
Date: Mon, 22 Dec 2003 22:43:40 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107213257612088@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107213018109724@msgid-missing>
Thanks for your help David, you too Greg.
Removing the --static from the LDFLAGS in the Makefile allowed udev to
compile properly with d-bus cvs (should be the same with 0.020, though I
haven't tested it).
As far as futher questions on sysfs. From what I understand (very
limited research) is that sysfs places everything in binary. What I
would like to know is, is this true? Also, is there any documentation on
libsysfs available?
Later,
WebmasterMattD (Sing joyfully to the Lord, you righteous; it is fitting
for the upright to praise him)
http://www.webmastermattd.net
=========Accountability n. Being held at gunpoint on the edge of a cliff and
asked to explain your actions.
David Zeuthen wrote:
>On Mon, 2003-12-22 at 22:31, WebmasterMattD wrote:
>
>
>>3. When I try to compile udev with USE_DBUS=true I get errors from gcc
>>stating that it has undefined references to the dbus functions (ie it
>>prints 'undefined reference to `dbus_connection_disconnect`).
>>
>>On the matter of question 3, I am currently playing around with udev-099
>>and d-bus cvs (checked out on the 22nd of December 2003 Aust EST, have
>>also tried d-bus-0.020 with the same errors being generated).
>>
>>
>>
>
>Yeah, I've had mixed luck with it myself. Btw, 0.20 of d-bus should be
>good enough you need d-bus CVS to run the python script that I've sent
>along with the d-bus patch.
>
>On FC1 it works despite warnings that the glibc .so needs to be
>available at run, but when I tried on debian/PPC the other day it
>refused to link until I removed the --static linking parameter. Then it
>worked great.
>
>So, my thinking is that d-bus needs some work before we can link
>statically with it, but I'm not sure.
>
>Cheers,
>David
>
>
>
>-------------------------------------------------------
>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
>
>
-------------------------------------------------------
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 prev parent reply other threads:[~2003-12-22 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 21:52 [udev] couple of newbie questions Greg KH
2003-12-22 21:56 ` David Zeuthen
2003-12-22 22:43 ` WebmasterMattD [this message]
2003-12-22 22:44 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 21:31 WebmasterMattD
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-107213257612088@msgid-missing \
--to=webmattd@webmastermattd.net \
--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).