On Thu, May 12, 2011 at 02:26:44PM -0500, George McCollister wrote: > On 04/29/2011 03:05 AM, Michael Olbrich wrote: > >>+HOST_OPKG_CONF_OPT := \ > >>> + $(HOST_AUTOCONF) \ > >>> + --enable-shave \ > >>> + --with-opkglockfile=/lock > >hmmm, this is relative to any DESTDIR, right? > > > I took some time to reevaluate this. > > Without --with-opkglockfile=/lock I get the following when opkg-cl > is used during my image creation: > Collected errors: > * opkg_conf_load: Could not create lock file > /home/georgem/workspace_armeb/platform-armeb-xscale/images/work_dir//usr/lib/opkg/lock: > No such file or directory.
... and the default for opkglockfile is /usr/lib/opkg/lock, so DESTDIR is used correctly. ../work_dir/ is probably empty at that point. Hmm, I don't think any package installs /lock, but maybe /.opkg-lock might be saver? Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list [email protected]
