So does that basically mean the I shouldn't use the development image
to do dev work.
From the sounds of it I'd be better taking the netbook image and yum
installing the dev packages.
It also sounds like the libudev-devel package is broken. The file
should be in the correct location and owned by the package.
On 22 Aug 2009, at 01:37, Rust Lynch <[email protected]> wrote:
On Fri, 2009-08-21 at 08:23 -0700, Glen Gray wrote:
Here's an example of the failures I'm seeing.
As you can see, it's configure is failing because it find libudev,
but
libudev and libudev-devel are installed. The libudev-devel installs
udev.pc, however the configure.ac seems to be looking for libudev
I can patch the configure script accordingly but Devicekit still
fails
to build as devkitd won't compile, errors out with undefined
references to various udev_device functions. I've listed all the udev
related packages from the repo and have them installed.
Strange... my netbook that pretty much has all of heaven and earth
installed has a /usr/lib/pkgconfig/libudev.pc, but it's not owned by
any
package.
hmm... ok, i can see that the libudev-devel packaging is
installing /lib/pkgconfig/libudev.pc, and in the post processing step
its linking to /usr/lib/pkgconfig/libudev.pc.
Untested wild guess: I think we still turn off the rpm post processing
when creating an image, so if libudev-devel was installed as part of
the
image creation then I suspect it's not creating the link.
See if you have a /lib/pkgconfig/libudev.pc in your chroot. If so
then
create a symbolic link to /usr/lib/pkgconfig/.
--rusty
_______________________________________________
Moblin dev Mailing List
[email protected]
To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org
once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists
