All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: Angolini Daiane-B19406 <B19406-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm for dylan][PATCH] amd-gpu-x11-bin-mx51: install dev symbolic link
Date: Fri, 21 Jun 2013 13:54:24 +0200	[thread overview]
Message-ID: <51C43EF0.8000600@digi.com> (raw)
In-Reply-To: <51ADF5A9C82CA04683FC48E400BD1652446670@039-SN2MPN1-013.039d.mgd.msft.net>

Hi Daiane,

On 21/06/13 13:47, Angolini Daiane-B19406 wrote:
> They are right on my rootfs on target.
>
> Do you think it makes any difference?

There is no functional difference. It will work just the same.

It's a bit of style. See the difference doing one link relative (z430) 
and the other absolute (z160):

root@ccimx53js:/usr/lib# ls -l lib2dz*
       23 Jun 21  2013 lib2dz160.so -> /usr/lib/lib2dz160.so.0
       14 Jun 20 17:28 lib2dz160.so.0 -> lib2dz160.so.1
   222959 Sep 25  2011 lib2dz160.so.1
       14 Jun 21  2013 lib2dz430.so -> lib2dz430.so.0
       14 Jun 20 17:28 lib2dz430.so.0 -> lib2dz430.so.1
   285066 Sep 25  2011 lib2dz430.so.1


Normally the libs do relative symlinks. You can verify it in your 
development machine.

-- 
Regards,

Javier Viguera


  reply	other threads:[~2013-06-21 11:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 20:42 [meta-fsl-arm for dylan][PATCH] amd-gpu-x11-bin-mx51: install dev symbolic link Daiane Angolini
2013-06-20 20:50 ` Otavio Salvador
2013-06-21  8:27 ` Javier Viguera
2013-06-21  9:08   ` Andrei Gherzan
2013-06-21 11:38   ` Otavio Salvador
2013-06-21 11:51     ` Angolini Daiane-B19406
2013-06-21 11:47   ` Angolini Daiane-B19406
2013-06-21 11:54     ` Javier Viguera [this message]
2013-06-21 11:59       ` Angolini Daiane-B19406

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=51C43EF0.8000600@digi.com \
    --to=javier.viguera@digi.com \
    --cc=B19406-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=meta-freescale@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.