On Sun, 2010-07-11 at 14:54 -0400, Frank Solensky wrote:
> Now I'm running into another problem with install that has been tripping
> me up in several other modules as well: attempting to install into the
> system directories rather than the destination I've given:
> /bin/sh ../libtool --mode=install
> /mnt/common/home/frank/.local/bin/install-check nm-modem-probe '/lib/udev'
> libtool: install: /mnt/common/home/frank/.local/bin/install-check
> nm-modem-probe /lib/udev/nm-modem-probe
> install: cannot create regular file `/lib/udev/nm-modem-probe': Permission
> denied
Add to .jhbuildrc:
module_autogenargs['NetworkManager'] = autogenargs + \
' --with-dbus-sys-dir=' + prefix + '/etc/dbus-1/system.d' + \
' --with-udev-dir=' + prefix + '/lib/udev'
The nm-modem-probe feature probably won't work, but it should at least
build. I don't know what nm-modem-probe does.
Regarding other modules trying to install to system directories, read
this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=581515
In summary, some modules are so low level, you can't have a functional
JHBuild sandbox version. Ideally, add these low level modules
to .jhbuildrc's skip, and install your distribution's dev packages. But
what if your distribution's packages are too old? That's where it gets
hard and there isn't any guide or manual to help out.
Regarding evince, evince shouldn't be installing to system directories,
so there may be a bug there.
--
Craig Keogh <[email protected]>
_______________________________________________
gnome-love mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-love