[pacman-dev] building from git erroneous
Building from commit fa06951d90fee028ece95fc7caab39fc7d35d55f generates the scripts pacman-db-upgrade, pacman-key and pkgdelta in the form DIR="/path/to/builddir/src/pacman/scripts"
LIBRARY="$DIR"/libmakepkg exec "$DIR"/.lib/pacman-key "$@"
so they hold a reference to the build directory. Building pacman with makepkg triggers the "reference to $srcdir" warning. However, I haven't bisected the latest commits yet.
On 25/10, Florian Weigelt wrote:
Building from commit fa06951d90fee028ece95fc7caab39fc7d35d55f generates the scripts pacman-db-upgrade, pacman-key and pkgdelta in the form DIR="/path/to/builddir/src/pacman/scripts"
LIBRARY="$DIR"/libmakepkg exec "$DIR"/.lib/pacman-key "$@"
so they hold a reference to the build directory. Building pacman with makepkg triggers the "reference to $srcdir" warning. However, I haven't bisected the latest commits yet.
Can't reproduce, which configure flags are you using?
On 25/10, Johannes Löthberg wrote:
On 25/10, Florian Weigelt wrote:
Building from commit fa06951d90fee028ece95fc7caab39fc7d35d55f generates the scripts pacman-db-upgrade, pacman-key and pkgdelta in the form DIR="/path/to/builddir/src/pacman/scripts"
LIBRARY="$DIR"/libmakepkg exec "$DIR"/.lib/pacman-key "$@"
so they hold a reference to the build directory. Building pacman with makepkg triggers the "reference to $srcdir" warning. However, I haven't bisected the latest commits yet.
Can't reproduce, which configure flags are you using?
Disregard that, can repro when building the package, hmm.
On 25/10, Johannes Löthberg wrote:
On 25/10, Johannes Löthberg wrote:
On 25/10, Florian Weigelt wrote:
Building from commit fa06951d90fee028ece95fc7caab39fc7d35d55f generates the scripts pacman-db-upgrade, pacman-key and pkgdelta in the form DIR="/path/to/builddir/src/pacman/scripts"
LIBRARY="$DIR"/libmakepkg exec "$DIR"/.lib/pacman-key "$@"
so they hold a reference to the build directory. Building pacman with makepkg triggers the "reference to $srcdir" warning. However, I haven't bisected the latest commits yet.
Can't reproduce, which configure flags are you using?
Disregard that, can repro when building the package, hmm.
So, since 1f8f0bd9ac4c11cdc1b9506f9f64d8192ecad4ee it for some reason installs the in-tree wrapper on install, d'oh.
participants (2)
-
Florian Weigelt
-
Johannes Löthberg