Search Criteria
Package Details: libim 3.15-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/libim.git (read-only, click to copy) |
---|---|
Package Base: | libim |
Description: | Imaging toolkit library |
Upstream URL: | https://www.tecgraf.puc-rio.br/im/ |
Licenses: | MIT |
Submitter: | None |
Maintainer: | blueowl |
Last Packager: | blueowl |
Votes: | 4 |
Popularity: | 0.066845 |
First Submitted: | 2010-07-22 08:52 (UTC) |
Last Updated: | 2024-07-25 08:38 (UTC) |
Dependencies (8)
- libpng (libpng-gitAUR, libpng-apngAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- fftw (fftw-amdAUR) (make)
- lsb-release (make)
- lua (make)
- lua51 (luajit-symlinksAUR) (make)
- lua52 (make)
- lua53 (make)
Latest Comments
1 2 Next › Last »
andrewkoz commented on 2024-07-12 00:20 (UTC) (edited on 2024-07-12 02:07 (UTC) by andrewkoz)
There are some problems with this package:
The md5 hash for im-3.15_Sources.tar.gz should be 9fb18d151dd8e7e540aa76ae409c37b2
If building in parallel then some targets are built at the same time as their dependencies which causes a race condition where the build fails if the targets are linked against dependencies that are still being built. To fix the build order add the following to package() in the PKGBUILD:
blueowl commented on 2019-02-07 13:41 (UTC) (edited on 2019-02-07 13:44 (UTC) by blueowl)
@wilmfone the message "../lib/Linux420_64/libim_process.so: file not recognized" looks suspicious.
It could be caused by various reasons. Please check that you have clean source directory, have enough memory and disk space.
If you still fail to build libim, I would like to ask you to continue troubleshooting via my email (not to spam these comments too much).
Some tips:
- Try to get PKGBUILD into fresh directory
- run makepkg with C locale to have English error messages
LC_ALL=C makepkg -L
- capture the log from the build
pkgbase-pkgver-pkgrel-arch-<function>.log
- what is your machine like: uname -a
- any other relevant info about how do you build, what (if anything) is special in your system, etc.
PS: There are many warnings while compiling the source. Even if they are ugly, mostly they are harmless and do not cause any problems. Nonetheless, I have been analyzing them and reporting to upstream.
wilmfone commented on 2019-02-04 15:13 (UTC)
New and more errors when watching in stderr during "makepkg": /usr/bin/ld: ../lib/Linux420_64/libim_process.so: file not recognized: file truncated collect2: Fehler: ld gab 1 als Ende-Status zurück make[1]: [../tecmake.mak:1607: ../lib/Linux420_64/libim_fftw.so] Fehler 1 make[1]: Das Ziel „build“ wurde wegen Fehlern nicht aktualisiert. make: [Makefile:22: im_fftw] Fehler 2 /usr/bin/ld: ../obj/im_jp2/Linux420_64/jas_stream.o: in function
jas_stream_tmpfile': jas_stream.c:(.text+0x6c2): Warnung:the use of
tmpnam' is dangerous, better use `mkstempAny ideas?
wilmfone commented on 2019-02-04 14:04 (UTC)
Problems when compiling im:
Tecmake: linking libim_lzo.so ... gcc -shared -o ../lib/Linux420_64/libim_lzo.so ../obj/im_lzo/Linux420_64/im_lzo.o ../obj/im_lzo/Linux420_64/minilzo.o -L../lib/Linux420_64 -lim -lpng -lz -lm /usr/bin/ld: -lim not found.
Can anyone help me what flag is missing here? Looks quite generic and missing either as a patch of the original sources...
ktamp commented on 2018-03-05 21:12 (UTC)
Please add 'lsb-release' to Makedepends list.
daurnimator commented on 2018-02-28 23:33 (UTC) (edited on 2018-02-28 23:35 (UTC) by daurnimator)
md5sums changed?
<hr>EDIT: Nevermind, sourceforge is down and serving:
We're sorry -- the Sourceforge site is currently in Disaster Recovery mode, and currently requires the use of javascript to function. Please check back later.
haawda commented on 2017-09-04 20:50 (UTC)
blueowl commented on 2017-09-04 11:41 (UTC)
daurnimator commented on 2017-06-26 06:42 (UTC)
1 2 Next › Last »