This is the first time I've seen makepkg not be able to create the $pkgdir/<dir> needed to package a file. I take it from the forum posts that this usually means that makepkg is trying to create the file in the actual filesystem instead of in the fakeroot $pkgdir. (eg: https://bbs.archlinux.org/viewtopic.php?pid=999088)
However, I cannot figure out what is causing it to do so on this simple package. The actual error I receive is:
I'm not sure what makepkg needs to tell it to put the packages in the $pkgdir from within the Makefile. Anyone else been bitten by this? Any quick fix?
> This is the first time I've seen makepkg not be able to create the > $pkgdir/<dir> needed to package a file. I take it from the forum posts > that this > usually means that makepkg is trying to create the file in the actual > filesystem > instead of in the fakeroot $pkgdir. (eg: > https://bbs.archlinux.org/viewtopic.php?pid=999088)
> However, I cannot figure out what is causing it to do so on this simple > package. The actual error I receive is:
> I'm not sure what makepkg needs to tell it to put the packages in the > $pkgdir > from within the Makefile. Anyone else been bitten by this? Any quick fix?
> This is the first time I've seen makepkg not be able to create the > $pkgdir/<dir> needed to package a file. I take it from the forum posts that this > usually means that makepkg is trying to create the file in the actual filesystem > instead of in the fakeroot $pkgdir. (eg: > https://bbs.archlinux.org/viewtopic.php?pid=999088)
> However, I cannot figure out what is causing it to do so on this simple > package. The actual error I receive is:
> I'm not sure what makepkg needs to tell it to put the packages in the $pkgdir > from within the Makefile. Anyone else been bitten by this? Any quick fix?
Any other thoughts on the issue are always appreciated. I'll try building another package that builds and installs fine in the chroot and see what it has in the Makefile. Weird issue :)
> package() { > msg "Packaging - $pkgname" > cd ${srcdir}/${pkgname#*-} > # make DESTDIR="${pkgdir}" install > make INSTALL_ROOT=$pkdir install
> }
> Is there something else I can try like patching the 'configure' file that > would help? This build is in a chroot -- I don't know if that makes a > difference > in the way makepkg behaves? The configure file is here: > http://www.3111skyline.com/dl/dt/trinity/arch/err/configure-tqca-tls.txt
> Any other thoughts on the issue are always appreciated. I'll try building > another package that builds and installs fine in the chroot and see what it > has > in the Makefile. Weird issue :)
>> I'm not sure what makepkg needs to tell it to put the packages in the $pkgdir >> > from within the Makefile. Anyone else been bitten by this? Any quick fix?
David C. Rankin wrote: > On 03/03/2012 04:39 PM, Allan McRae wrote: >>> I'm not sure what makepkg needs to tell it to put the packages in the $pkgdir >>>> from within the Makefile. Anyone else been bitten by this? Any quick fix?
>> make INSTALL_ROOT=$pkdir install
> What determines whether you need:
> make DESTDIR="${pkgdir}" install
> or
> make INSTALL_ROOT="${pkgdir}" install
> ??
> Can you grep something before building and tell?
A lot of software uses the GNU autotools to generate the makefiles. You can tell by the presence of the files configure.ac (or configure.in) and Makefile.am. For most of those DESTDIR should work (unless the developer added some custom rules that don't follow the usual practice).
For other software, there is no easy way to tell. I have seen DESTDIR, DEST_DIR and INSTALL_ROOT among others (plus some software does not have a way to install like that and you need to change the prefix and cross your fingers that it will work).
> On 03/03/2012 04:39 PM, Allan McRae wrote: >>> I'm not sure what makepkg needs to tell it to put the packages in the $pkgdir >>>> from within the Makefile. Anyone else been bitten by this? Any quick fix?
>> make INSTALL_ROOT=$pkdir install
> What determines whether you need:
> make DESTDIR="${pkgdir}" install
> or
> make INSTALL_ROOT="${pkgdir}" install
> ??
> Can you grep something before building and tell?
The Makefile....
I just find it's easier to just let it puke and then have a look at the Makefile
BTW how is trinity going?
I haven't looked at trinity for some time, as I dropped out.