We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When compiling "32-bit binaries on 64-bit machine" option, we have 32-bit binaries in /usr/lib64 folder:
wiselord lib # file /usr/lib64/apulse/libpulse.so.0 /usr/lib64/apulse/libpulse.so.0: ELF 32-bit LSB shared object, Intel 80386...,
because /usr/lib is usually just a link to /usr/lib64.
Maybe it'd be better to place apulse libraries to /usr/lib32/apulse by default when "CFLAGS=-m32" is used?
Also this can allow to compile both 32/64 apulse binaries at the same time
The text was updated successfully, but these errors were encountered:
Fixed in 2b44920.
Now you can select where to put shared libraries by setting APULSEPATH parameter: cmake -DCMAKE_INSTALL_PREFIX=/use -DAPULSEPATH=/usr/lib32/apulse ..
cmake -DCMAKE_INSTALL_PREFIX=/use -DAPULSEPATH=/usr/lib32/apulse ..
Sorry, something went wrong.
No branches or pull requests
When compiling "32-bit binaries on 64-bit machine" option, we have 32-bit binaries in /usr/lib64 folder:
because /usr/lib is usually just a link to /usr/lib64.
Maybe it'd be better to place apulse libraries to /usr/lib32/apulse by default when "CFLAGS=-m32" is used?
Also this can allow to compile both 32/64 apulse binaries at the same time
The text was updated successfully, but these errors were encountered: