-
Notifications
You must be signed in to change notification settings - Fork 132
pngquant: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory #93
Comments
I think you already saw #51. As I said there this is an issue with a dependency of this loader, so please report it over there. Thanks |
Can we reopen this ? I am hitting the same issue on alpine. This seriously increase our images sizes. I think you shouldn't use a library that ship deprecated binaries on their repo. |
@kopax how do you propose this issue? |
I would say to use to use the |
@kopax that's something what a dependency of this loader could do. This package is not much more than a wrapper for imagemin packages. So this is not something we should solve. |
@tcoopman is there an option that would allow the use of it on alpine linux ? I think this need to be solve at some point... How about creating symlinks of host binaries upon install ? |
It should certainly be possible. But I think you are better of looking for a solution at the correct dependency repo. Maybe you can find a solution over there. If you find a solution, feel free to link it here or create a PR for the readme |
@tcoopman do you have the repo url ? thanks! |
If you having this issue on linux this will solve it for you...if you need sudo permissions add them |
#93 (comment) I tried it on CentOS 7, I think it should be same, did I miss something? |
@wenisy I checked and Also check this thread for more on that Tell me how that goes. |
@iamcaleberic I gave you a thumb up, hope you got the notification. |
None of the above fixes worked for me, but this one does:
|
Thanks @slamorte , helped me |
Thanks @slamorte. Had to use The following worked for me: |
@iamcaleberic this worked for me. |
I have a build process running on a remote machine via Jenkins. I am using NPM and triggering a build with the following command:
My
webpack.production.config.js
section for image-webpack-loader looks like this:For every png file webpack is trying to load, I get messages that end with:
If I manually go into this directory and execute
./pngquant
, I can indeed see that it cannot find that shared object file.Strangely enough, on this red hat machine I am building on, this shared object is definitely available. See the output of the
locate
command below:So what's the problem here?
I have seen many references claiming that following should solve this problem:
npm install image-webpack pngquant
(did not work)brew install libpng
sudo apt-get install libpng-dev
I had the ability to run the
brew
command on my local development machine -- which I believe gave me a temporary workaround for developing.Unfortunately, I do not have admin privileges on my build machine, and these fixes ultimately do not get to the root of the issue.
Installing a system-wide binary should not be necessary via an package dependency manager like NPM, so I'm really trying to get at the root of the issue here and wondering if anybody has an ideas.
I even tried reverting to an older image-webpack-loader version (2.0.0 from 3.3.0) because I saw someone mention that this issue did not occur for 2.x.x. Nevertheless, this did not change my outcome.
The text was updated successfully, but these errors were encountered: