You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Later when we actually configure drgn before compiling it I see:
19:47:13 checking for libkdumpfile... no
I don’t think that something is wrong with something changing in the drgn repo because the sdb nightlies have been passing (they compile both drgn and libkdumpfile from source and actively use kdumps)
Pavel tried running ./buildpkg.sh drgn in a bootstrap VM and saw the same problem. I believe it may have something to do with the libkdumpfile debian package not providing everything that drgn needs to detect that it is installed on the system during compile time (e.g. maybe the specific pkgconf/pkg-config metadata?)
The text was updated successfully, but these errors were encountered:
sdimitro
changed the title
Drgn does not pick up Libkdumpfile installation during compilation
Drgn does not pick up Libkdumpfile dependency during compilation
Nov 13, 2020
There is a problem on how compile time dependencies work in the case of
drgn
- specificallylibkdumpfile
.I noticed this on a trunk VM from today:
Then looked at the actual linux-pkg job: http://ops.jenkins.delphix.com/job/devops-gate/job/master/job/linux-pkg/job/master/job/build-package/job/drgn/job/pre-push/5/console
Even though I see the dependency being installed:
Later when we actually configure
drgn
before compiling it I see:I don’t think that something is wrong with something changing in the drgn repo because the sdb nightlies have been passing (they compile both drgn and libkdumpfile from source and actively use kdumps)
Pavel tried running
./buildpkg.sh drgn
in a bootstrap VM and saw the same problem. I believe it may have something to do with the libkdumpfile debian package not providing everything thatdrgn
needs to detect that it is installed on the system during compile time (e.g. maybe the specificpkgconf
/pkg-config
metadata?)The text was updated successfully, but these errors were encountered: