From: Parke <parke.nexus@gmail.com>
To: voidlinux <voidlinux@googlegroups.com>
Subject: Re: Any way to get Adobe Acrobat reader on Void Linux?
Date: Wed, 3 May 2023 12:52:23 -0700 (PDT) [thread overview]
Message-ID: <680c3b83-67c4-4f72-b0c7-8f5530193c99n@googlegroups.com> (raw)
In-Reply-To: <20230503105851.jeg75crmklnpil4h@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1773 bytes --]
On Wednesday, May 3, 2023 at 3:58:53 AM UTC-7 Mayuresh wrote:
$ file /opt/Adobe/Reader9/Reader/intellinux/bin/acroread
/opt/Adobe/Reader9/Reader/intellinux/bin/acroread: ELF 32-bit LSB
executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter
/lib/ld-linux.so.2, for GNU/Linux 2.2.5, stripped
$ ldd /opt/Adobe/Reader9/Reader/intellinux/bin/acroread
not a dynamic executable
Strange that ldd cannot read the executable. But maybe that always happens
for 32-bit executables on 64-bit system? I don't have enough experience to
know.
Is the file /lib/ld-linux.so.2 present on your system? That file should be
the 32-bit dynamic linker.
Whereas on my 64 bit system, the 64-bit dynamic linker appears to
be /lib64/ld-linux-x86-64.so.2.
$ ldd /bin/ls
linux-vdso.so.1 (0x00007fff74385000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1
(0x00007f26d9c1f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f26d99f7000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0
(0x00007f26d9960000)
/lib64/ld-linux-x86-64.so.2 (0x00007f26d9c7d000)
$ file /bin/ls
/bin/ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=[snip], for GNU/Linux 3.2.0, stripped
Sorry I cannot offer more assistance.
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/680c3b83-67c4-4f72-b0c7-8f5530193c99n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2417 bytes --]
next prev parent reply other threads:[~2023-05-03 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 15:54 Mayuresh
2023-05-01 18:10 ` Parke
2023-05-03 10:58 ` Mayuresh
2023-05-03 19:52 ` Parke [this message]
2023-05-03 20:06 ` Leah Neukirchen
2023-05-04 1:02 ` Mayuresh
2023-05-04 4:26 ` Mayuresh
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=680c3b83-67c4-4f72-b0c7-8f5530193c99n@googlegroups.com \
--to=parke.nexus@gmail.com \
--cc=voidlinux@googlegroups.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 NNTP newsgroup(s).