Skip to content
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

alpine #630

Closed
dcharbonnier opened this issue Nov 22, 2016 · 10 comments
Closed

alpine #630

dcharbonnier opened this issue Nov 22, 2016 · 10 comments
Labels

Comments

@dcharbonnier
Copy link

Reading the issues it seams very hard to make it work, would it be possible to officially support alpine ? Can we imagine a prebuild version statically compiled ?

@dcharbonnier
Copy link
Author

the solution is easy, hope this will help others :
RUN apk add vips-dev -q --no-progress --no-cache --repository http://nl.alpinelinux.org/alpine/edge/testing

@lovell
Copy link
Owner

lovell commented Nov 22, 2016

Glad you got it working. Whilst vips is available and regularly updated for Alpine via apk then there's little need to precompile for musl libc. http://pkgs.alpinelinux.org/packages?name=vips

@lecstor
Copy link

lecstor commented Nov 27, 2016

@dcharbonnier thank you! after everything I've tried after reading all the threads, it appears that that has finally got it working for me. (the docker build completed successfully for the first time anyway)

@tmcgannon
Copy link

Will this library ever be moved out of /edge/testing? I'd like to use it on Alpine:3.5 without building it myself.

@lovell
Copy link
Owner

lovell commented Mar 6, 2017

@tmcgannon Please ask your question over at https://github.com/alpinelinux/aports

"All new packages goes to testing first. Package will be moved to main if there positive feedback or other good reasons. Packages in testing are not included in stable builds, but are only built for edge." https://wiki.alpinelinux.org/wiki/Aports_tree#testing

@teohhanhui
Copy link
Contributor

For Linux-based operating systems such as Alpine that use musl libc, the smaller stack size means libvips' cache should be disabled via sharp.cache(false) to avoid a stack overflow.

Is this still relevant? And if the cache doesn't work properly on musl anyway, shouldn't it be detected and disabled? Or should that actually be the job of the APKBUILD?

@lovell
Copy link
Owner

lovell commented Apr 20, 2017

@teohhanhui It depends on how complex the processing pipeline and therefore how deep the stack becomes. Probably best to test your specific use case(s) and find out :)

@teohhanhui
Copy link
Contributor

teohhanhui commented Apr 20, 2017

But the app shouldn't be concerned about whether it's glibc or musl libc under the hood, should it? I think it's the wrong level to be addressing that problem...

@Juljan
Copy link

Juljan commented Feb 24, 2019

Hello,

# apk add vips-dev -q --no-progress --no-cache --repository http://nl.alpinelinux.org/alpine/edge/testing
ERROR: unsatisfiable constraints:
  pc:fftw3 (missing):
    required by: vips-dev-8.7.4-r1[pc:fftw3] vips-dev-8.7.4-r1[pc:fftw3] vips-dev-8.7.4-r1[pc:fftw3]

Any idea ?

@lovell
Copy link
Owner

lovell commented Feb 24, 2019

Repository owner locked and limited conversation to collaborators Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants