-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make rpm is using host libraries #909
Comments
Okay, I think I understand what's going on. I noticed that if I build debs from the commit before ca8b5af and install them, then the issue disappears. So I wondered if the issue was dependent on what was installed on the system. I came back to the commit before So it seems that, starting from ca8b5af, By the way, here's the full build output: https://gist.github.com/3512064 |
Workaround: uninstall old zfs packages from the system before building the new ones. |
I always test debian squeeze and haven't seen this issue. Based on your analysis it looks like that's because I always do it with a clean spl/zfs install. The error and workaround suggest that it's somehow accidentally picking up and older version of libzfs.so. Do you have any idea where it might be finding it? |
Well...
So, starting from ca8b5af, |
|
mount_zfs depends on libzpool for zfs_prop_written since 330d06f. Unfortunately, the Makefile for mount_zfs has not been modified to reflect this. As a result, libtool doesn't know about the dependency, which may result in the wrong libzpool being used during the build (e.g. the libzpool from the system instead of the libzpool from the build directory). This patch adds the dependency to fix the issue. Fixes openzfs#909.
Fixed in #913. |
Thank you. |
Signed-off-by: Paul Dagnelie <[email protected]> Co-authored-by: Don Brady <[email protected]>
Note: previous title was "make rpm: undefined reference to zfs_prop_written".
With latest git master, on Debian squeeze,
make rpm
fails:Note that, surprisingly, normal
make
(withoutrpm
) works.A bissection indicates the issue is caused by ca8b5af.
The text was updated successfully, but these errors were encountered: