mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] The second symbolic links are not copied to the target
Date: Thu, 5 Jul 2018 14:22:23 +0200	[thread overview]
Message-ID: <20180705122223.fr6w26vqy3qww35d@pengutronix.de> (raw)
In-Reply-To: <CAEt18EWT6k0cTycNK4W6DvBQBS9Rv0ueN6Wb+-XAZRdbWV1EPQ@mail.gmail.com>

Hi,

On Thu, Jul 05, 2018 at 01:02:47PM +0200, Alejandro Vázquez wrote:
> None of the two I think. This was changed in commit
> > f13787aca6bc51976cbc34be7262683ccd134474, log message was:
> > ptxd_install_shared: don't install last link
> > It's only needed at build time.
> 
> 
> Fine but in the ptxdist documentation
> <https://www.ptxdist.org/doc/ref_manual.html#install-lib> it indicates that
> the file *.so is copied.

This is outdated. I need to fix that.

> Is this causing any actual problems?

These links should not be necessary at runtime. That's how library
versioning on Linux works.
If you check your desktop Linux, you'll notice, that the last link is in
the devel package: It's only needed at built time.

> Yes. At least it gives problems with Java applications.
> .......
>  [Failed to open library /usr/lib/classpath/libjavanio.so:
> /usr/lib/classpath/libjavanio.so: cannot open shared object file: No such
> file or directory]
>  [Failed to open library ./libjavanio.so: ./libjavanio.so: cannot open
> shared object file: No such file or directory]
>  [Failed to open library /usr/lib/jni/libjavanio.so:
> /usr/lib/jni/libjavanio.so: cannot open shared object file: No such file or
> directory]
> ......
> 
> It also happens with some Gstreamer plugins.
> 
> (gst-plugin-scanner:252): GStreamer-WARNING **: Failed to load plugin
> '/usr/lib/gstreamer-1.0/libgstimxg2d.so': libGAL.so: cannot open shared
> object file: No such file or directory

These libraries are broken. I expect they don't have a soname (you can
check that with 'readelf -d <filename>').

You need to create the link manually with 'install_link'.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-07-05 12:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01  4:28 Alejandro Vázquez
2018-07-05  8:25 ` Guillermo Rodriguez Garcia
2018-07-05 11:02   ` Alejandro Vázquez
2018-07-05 12:22     ` Michael Olbrich [this message]
2018-07-05 12:50       ` Guillermo Rodriguez Garcia
2018-07-06  9:54         ` Michael Olbrich
2018-07-06 10:30           ` Guillermo Rodriguez Garcia
2018-07-10  6:48             ` Michael Olbrich

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180705122223.fr6w26vqy3qww35d@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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