From: David Pirotte <david@altosw.be>
To: Daniele <teikfaiv@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Guile-CV: Not a GRAY, RGB nor an RGBA image "sand.tif"
Date: Wed, 6 Dec 2017 16:43:52 -0200 [thread overview]
Message-ID: <20171206164352.4f95ff04@capac> (raw)
In-Reply-To: <CAFmhb5FCE7puQqLZKu79ceRVEmMFMArZ2KEg4Gc6Mki-eae9RA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2945 bytes --]
Hi Daniele,
this is a long answer, please read carefully, and apply all the steps
meticulously...
> > Did you install Vigra 'manually?
> > What is the version of Vigra?
You forgot to answer the above question, but I believe, because of the (incomplete)
'ldd libvigra_c.so' report you sent, that you installed Vigra manually, which is
perfect (and expected): debian buster still uses 1.10, and Guile-CV needs Vigra 1.11
(to be fully correct, the libvigra_c upon which Guile-CV depends needs Vigra 1.11):
It is also a lot better in the long run, debian, even buster, is far too
slow 'for us', as you can see (Vigra 1.11 has been released a while ago...).
However, when you install Vigra manually, you are responsible for the installation
of the image format libraries you intend to use, and you are missing practically all
of them, let's fix this, see below.
> > What is the last commit of vigra_c on your side? (just go in the
> > directory where you cloned, run gilt log and grab the first line for me).
>
> commit 691b189b05b0e0734376510cbdb256d30725ec96 (HEAD -> master,
> origin/master, origin/HEAD)
Perfect.
> > David
as an aside note, please configure your email so it does not wrap long lines
so you can copy paste 'terminal output', and manually ask for wrapping text
lines,,, thanks!
> linux-vdso.so.1 (0x00007fffaefc0000)
> libvigraimpex.so.11 => /usr/local/lib/libvigraimpex.so.11
> ...
This is largely incomplete. Let's 'trick' to solve this and try to save some time
as well, please try the following:
1- install libvigraimpex-dev
sudo apt-get install libvigraimpex-dev
this will install all Vigra dependencies as specified by the debian
team: it will install all image libraries development files for all
image format Vigra is capable of handling
2- recompile Vigra
cd /your-vigra-source-tree-location/
make clean
cmake \
-DCMAKE_INSTALL_PREFIX=/opt/vigra \
-DCMAKE_BUILD_TYPE=RELEASE
[ in the above steps, substitute the PREFIX as
[ appropriate ... I suggest you keep the one you had to
[ simplify (otherwise remember to (re)configure
[ in /etc/ld.so.conf.d//vigra.conf and run ldconfig as
[ root ...
at this point, cmake will list all format it will accept, so
you can double check ...
make
make install
3- recompile libvigra_c
make clean
cmake \
-DCMAKE_INSTALL_PREFIX=/opt/vigra_c \
-DCMAKE_BUILD_TYPE=RELEASE
[ in the above steps, substitute the PREFIX for the
[ one used above ... remember to (re)configure
[ in /etc/ld.so.conf.d//vigra_c.conf and run ldconfig as
[ root ...
make
make install
4- you may safely remove libvigraimpex-dev if you wish, we are not
using it anyway...
Then try make check in Guile-CV, then make install, and ... it should be fine.
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-06 18:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 15:30 Guile-CV: Not a GRAY, RGB nor an RGBA image "sand.tif" Daniele
2017-12-05 19:54 ` David Pirotte
2017-12-05 21:04 ` Daniele
2017-12-05 21:55 ` David Pirotte
2017-12-05 23:42 ` Mark H Weaver
2017-12-06 2:23 ` David Pirotte
2017-12-06 3:34 ` Mark H Weaver
2017-12-06 8:47 ` tomas
2017-12-06 7:12 ` Daniele
[not found] ` <CAFmhb5GxuLK2k+2z_JzSPBx3dV7wVP=wG55HFXFdHsKCp96YKQ@mail.gmail.com>
2017-12-06 14:47 ` David Pirotte
2017-12-06 15:20 ` Daniele
2017-12-06 18:43 ` David Pirotte [this message]
2017-12-06 20:27 ` Daniele
2017-12-06 23:49 ` David Pirotte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171206164352.4f95ff04@capac \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=teikfaiv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).