From: "Georg Nikodym" <georgn@somanetworks.com>
To: hiren_mehta@agilent.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with devfsd compilation
Date: Thu, 1 Feb 2001 13:52:12 -0500 (EST) [thread overview]
Message-ID: <14969.45148.886179.74191@somanetworks.com> (raw)
In-Reply-To: <FEEBE78C8360D411ACFD00D0B747797188097A@xsj02.sjs.agilent.com>
In-Reply-To: <FEEBE78C8360D411ACFD00D0B747797188097A@xsj02.sjs.agilent.com>
>>>>> "hm" == hiren mehta <hiren_mehta@agilent.com> writes:
hm> Hi, I am trying to compile devfsd on my system running RedHat
hm> linux 7.0 (kernel 2.2.16-22). I get the error "RTLD_NEXT"
hm> undefined. I am not sure where this symbol is defined. Is there
hm> anything that I am missing on my system.
Oh yeah, here's the two other things I forgot.
The install target of the devfsd GNUmakefile attempts to copy the
devfsd.8 man page into /usr/man/man8 which doesn't exist. RH7 has
its man pages in /usr/share/man though you might prefer
/usr/local/man, whatever. I just changed the GNUmakefile.
Also, RH7's /etc/rc.sysinit can already start devfsd automatically
with the following line:
[ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev
So, all you have to do is create an empty file /dev/.devfsd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-01 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 18:37 problem with devfsd compilation hiren_mehta
2001-02-01 18:44 ` Georg Nikodym
2001-02-01 18:45 ` Alan Cox
2001-02-02 6:25 ` Michael B. Trausch
2001-02-01 18:52 ` Georg Nikodym [this message]
2001-02-02 11:36 ` problems " Paul Collins
2001-02-02 8:21 ` problem " Michael B. Trausch
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 19:26 Andris Pavenis
2001-02-02 2:50 Frédéric L. W. Meunier
2001-02-02 14:46 ` Georg Nikodym
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=14969.45148.886179.74191@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=hiren_mehta@agilent.com \
--cc=linux-kernel@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