mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Alejandro Vázquez" <vazlup@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] The second symbolic links are not copied to the target
Date: Thu, 5 Jul 2018 13:02:47 +0200	[thread overview]
Message-ID: <CAEt18EWT6k0cTycNK4W6DvBQBS9Rv0ueN6Wb+-XAZRdbWV1EPQ@mail.gmail.com> (raw)
In-Reply-To: <CABDcavbryk0uW40iqUBBbubtUkPw4+byJ8ynrG897SHEo=0uxg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2175 bytes --]

Thanks, Guillermo!

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.

Is this causing any actual problems?


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


2018-07-05 10:25 GMT+02:00 Guillermo Rodriguez Garcia <
guille.rodriguez@gmail.com>:

> Hi there,
>
> 2018-07-01 6:28 GMT+02:00 Alejandro Vázquez <vazlup@gmail.com>:
> > Hi!
> > I've come across the following problem:
> > When installing classpath, the second symbolic links are not copied to
> the
> > target.
> > This should not happen as the library is installed as install_lib and you
> > should install the second symbol links.
> > I came from an older version of ptxdist and this didn't happen.
> > ptxdist --version: 2018.06.0
> >
> > I'm not sure if it's a bug or a problem of mine.
>
> 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.
>
> Is this causing any actual problems?
>
> BR,
>
> Guillermo Rodriguez Garcia
> guille.rodriguez@gmail.com
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de

[-- Attachment #1.2: Type: text/html, Size: 5111 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-07-05 11:02 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 [this message]
2018-07-05 12:22     ` Michael Olbrich
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=CAEt18EWT6k0cTycNK4W6DvBQBS9Rv0ueN6Wb+-XAZRdbWV1EPQ@mail.gmail.com \
    --to=vazlup@gmail.com \
    --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