Linux SNPS ARC Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org, libc-alpha@sourceware.org,
	ahajkova@redhat.com
Subject: Re: How to elf/tst-ldconfig-* in cross test setup
Date: Wed, 11 Mar 2020 17:36:24 -0400	[thread overview]
Message-ID: <xn36ae60br.fsf@greed.delorie.com> (raw)
In-Reply-To: <14513500-39f7-00a3-1d1c-4d8e4d6f24a3@synopsys.com> (message from Vineet Gupta via Libc-alpha on Wed, 11 Mar 2020 19:56:21 +0000)

Vineet Gupta via Libc-alpha <libc-alpha@sourceware.org> writes:
> The issue is expected src-path for dso.
>
> | [pid   168] renameat(AT_FDCWD, "/usr/lib/tst-ldconfig-ld-mod.so", AT_FDCWD,
> |     "/tmp/tst-ldconfig/libldconfig-ld-mod.so") = -1 EXDEV
> |      (Invalid cross-device link)
>
> In cross setup, /usr/lib needs to be the host path where test is built or the dso
> needs to be copied over to target at the canonical location. I'm not sure what the
> right approach is so any pointers would be great.

This rename should be happening inside the test-container, in a
subdirectory of the build, so should not be a cross-dev link.  Are you
trying to run these tests manually?


_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  reply	other threads:[~2020-03-11 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 19:56 How to elf/tst-ldconfig-* in cross test setup Vineet Gupta
2020-03-11 21:36 ` DJ Delorie [this message]
2020-03-11 21:50   ` Vineet Gupta
2020-03-11 22:07     ` DJ Delorie
2020-03-11 22:14       ` Vineet Gupta
2020-03-11 22:21         ` Vineet Gupta
2020-03-11 22:28           ` DJ Delorie
2020-03-11 22:38             ` Vineet Gupta
2020-03-11 22:56               ` Vineet Gupta
2020-03-12  0:53                 ` Vineet Gupta
2020-03-11 22:23         ` DJ Delorie

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=xn36ae60br.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=ahajkova@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-snps-arc@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox