From: Thomas Penteker <tek@serverop.de>
To: linux-hotplug@vger.kernel.org
Subject: firmware issues #2?
Date: Fri, 23 Apr 2010 16:55:24 +0000 [thread overview]
Message-ID: <20100423165524.GA32238@serverop.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
Hello,
calling configure of udev-153 gives me the following:
% ./configure --disable-extras --disable-introspection --with-firmware-path=/lib/SOMETHINGUNIQUE:/lib/foo
(...)
firmware path:
(...)
Compliation proves this:
% make V=1 2>&1 | grep -- -DFIRMWARE
gcc -DHAVE_CONFIG_H -I. -include ./config.h -I./libudev
-DSYSCONFDIR=\""/usr/etc"\" -DLIBEXECDIR=\""/usr/libexec"\" -DFIRMWARE_PATH=""
-g -O2 -MT extras/firmware/extras_firmware_firmware-firmware.o -MD -MP -MF
extras/firmware/.deps/extras_firmware_firmware-firmware.Tpo -c -o
extras/firmware/extras_firmware_firmware-firmware.o `test -f
'extras/firmware/firmware.c' || echo './'`extras/firmware/firmware.c
Correcting the FIRMWARE_PATH variable in Makefile fixes the issue.
So I think the firmware-path still is broken (but in a different way).
kind regards, Thomas Penteker
--
dynamic software linking table corrupted
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-04-23 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 16:55 Thomas Penteker [this message]
2010-04-23 19:25 ` firmware issues #2? Robby Workman
2010-04-24 19:42 ` 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=20100423165524.GA32238@serverop.de \
--to=tek@serverop.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).