Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 850064

Summary: app-text/master-pdf-editor-5.8.52: doesn't work on arm64, installs amd64 binary, arm64 bin available for another version
Product: Gentoo Linux Reporter: korte
Component: Current packagesAssignee: João Santos <joaompssantos>
Status: UNCONFIRMED ---    
Severity: normal CC: proxy-maint
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Ebuild for arm64

Description korte 2022-06-06 09:24:43 UTC
I installed app-text/master-pdf-editor-5.8.52 on arm64 (Pi400) and get: 

masterpdfeditor5
bash: /opt/bin/masterpdfeditor5: cannot execute binary file: Exec format error

ls -l /opt/bin/masterpdfeditor5 
lrwxrwxrwx 1 root root 37 Jun  6 10:57 /opt/bin/masterpdfeditor5 -> ../master-pdf-editor/masterpdfeditor5

file /opt/master-pdf-editor/masterpdfeditor5
/opt/master-pdf-editor/masterpdfeditor5: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=87f8039b1285109d693f7651d81005df8610b980, stripped


At https://code-industry.net/free-pdf-editor/ there is a "For arm64:
master-pdf-editor-5.8.46-qt5.arm64.tar.gz". Since of the old version for arm64 the recent packages should be -arm64 or -* imho. https://code-industry.net/public/master-pdf-editor-5.8.46-qt5.arm64.tar.gz

The ~arm64 from the homepage works for me, except that it reports a more recent version on the homepage, though there is no newer version for arm64.
Comment 1 João Santos 2022-06-26 08:32:04 UTC
I am not sure I understand. Did you tried to change the ebuild to install the arm64 version?

I don't have a arm64 device where I can test the ebuild.
Comment 2 korte 2022-06-26 09:07:26 UTC
(In reply to João Santos from comment #1)
> I am not sure I understand. Did you tried to change the ebuild to install
> the arm64 version?

No. I just downloaded the file from the homepage and unpacked it.

> 
> I don't have a arm64 device where I can test the ebuild.

At the moment I run RaspberryPi OS but I can change to Gentoo to test an ebuild. Can you create an ebuild and publish it?


https://code-industry.net/public/master-pdf-editor-5.8.65-qt5.x86_64.tar.gz
https://code-industry.net/public/master-pdf-editor-5.8.46-qt5.arm64.tar.gz

VERSION=5.8.65 #for x86_64, -* since there is no other ARCH available, imho
VERSION=5.8.46 #for arm64 (no -* necessary, download for 5.8.46 is available for x86_64)

ARCH=[x86_64|arm64]

https://code-industry.net/public/master-pdf-editor-$VERSION-qt5.$ARCH.tar.gz
Comment 3 João Santos 2022-06-26 11:05:51 UTC
(In reply to korte from comment #2)
> (In reply to João Santos from comment #1)
> > I am not sure I understand. Did you tried to change the ebuild to install
> > the arm64 version?
> 
> No. I just downloaded the file from the homepage and unpacked it.
> 
> > 
> > I don't have a arm64 device where I can test the ebuild.
> 
> At the moment I run RaspberryPi OS but I can change to Gentoo to test an
> ebuild. Can you create an ebuild and publish it?
> 
> 
> https://code-industry.net/public/master-pdf-editor-5.8.65-qt5.x86_64.tar.gz
> https://code-industry.net/public/master-pdf-editor-5.8.46-qt5.arm64.tar.gz
> 
> VERSION=5.8.65 #for x86_64, -* since there is no other ARCH available, imho
> VERSION=5.8.46 #for arm64 (no -* necessary, download for 5.8.46 is available
> for x86_64)
> 
> ARCH=[x86_64|arm64]
> 
> https://code-industry.net/public/master-pdf-editor-$VERSION-qt5.$ARCH.tar.gz

Not sure how these would work. Does the ebuild system recognise these variables?
Comment 4 João Santos 2022-06-26 11:06:45 UTC
Created attachment 787763 [details]
Ebuild for arm64

In the meanwhile can you test the attached ebuild?
Comment 5 korte 2022-06-26 15:51:28 UTC
(In reply to João Santos from comment #4)
> Created attachment 787763 [details]
> Ebuild for arm64
> 
> In the meanwhile can you test the attached ebuild?

It didn't work. What I did:

cd $(portageq get_repo_path / gentoo)
cd app-text/master-pdf-editor
ekeyword ~arm64 master-pdf-editor-5.8.52.ebuild
ebuild master-pdf-editor-5.8.52.ebuild manifest
emerge -va app-text/master-pdf-editor-5.8.52

 * Package:    app-text/master-pdf-editor-5.8.52
 * Repository: gentoo
 * Maintainer: joaompssantos@gmail.com proxy-maint@gentoo.org
 * USE:        arm64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   ccache network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.52/work
>>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.52/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-text/master-pdf-editor-5.8.52/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-text/master-pdf-editor-5.8.52/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-text/master-pdf-editor-5.8.52
 * ERROR: app-text/master-pdf-editor-5.8.52::gentoo failed (install phase):
 *   The source directory '/var/tmp/portage/app-text/master-pdf-editor-5.8.52/work/master-pdf-editor-5' doesn't exist
 *
 * Call stack:
 *            ebuild.sh, line  770:  Called __ebuild_main 'install'
 *   phase-functions.sh, line 1059:  Called __dyn_install
 *   phase-functions.sh, line  577:  Called die
 * The specific snippet of code:
 *              die "The source directory '${S}' doesn't exist"
 *
 * If you need support, post the output of `emerge --info '=app-text/master-pdf-editor-5.8.52::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/master-pdf-editor-5.8.52::gentoo'`.
 * The complete build log is located at '/var/log/portage/build/app-text/master-pdf-editor-5.8.52:20220626-154308.log.gz'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-text/master-pdf-editor-5.8.52/temp/build.log.gz'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/master-pdf-editor-5.8.52/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/master-pdf-editor-5.8.52/empty'
 * S: '/var/tmp/portage/app-text/master-pdf-editor-5.8.52/work/master-pdf-editor-5'
Comment 6 korte 2022-06-26 19:01:04 UTC
I forgot to add:

wget https://850064.bugs.gentoo.org/attachment.cgi?id=787763 in the app-text/master-pdf-editor
Comment 7 João Santos 2022-06-26 20:45:00 UTC
The "new" ebuild I provided as an attachement should be master-pdf-editor-5.8.46.ebuild and not master-pdf-editor-5.8.52.ebuild.

It seems that you did not use the correct one, the ebuild extracts the version number from the file name and there is no arm64 build for 5.8.52 as far as I could tell.
Comment 8 korte 2022-06-26 21:03:01 UTC
cd $(portageq get_repo_path / gentoo)
cd app-text/master-pdf-editor
wget https://850064.bugs.gentoo.org/attachment.cgi?id=787763 -O master-pdf-editor-5.8.46.ebuild
ekeyword ~arm64 master-pdf-editor-5.8.46.ebuild
ebuild master-pdf-editor-5.8.46.ebuild manifest
emerge -va =app-text/master-pdf-editor-5.8.46

 * Package:    app-text/master-pdf-editor-5.8.46
 * Repository: gentoo
 * Maintainer: joaompssantos@gmail.com proxy-maint@gentoo.org
 * USE:        arm64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   ccache network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work
>>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-text/master-pdf-editor-5.8.46
 * ERROR: app-text/master-pdf-editor-5.8.46::gentoo failed (install phase):
 *   The source directory '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5' doesn't exist
 *
 * Call stack:
 *            ebuild.sh, line  770:  Called __ebuild_main 'install'
 *   phase-functions.sh, line 1059:  Called __dyn_install
 *   phase-functions.sh, line  577:  Called die
 * The specific snippet of code:
 *              die "The source directory '${S}' doesn't exist"
 *
 * If you need support, post the output of `emerge --info '=app-text/master-pdf-editor-5.8.46::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/master-pdf-editor-5.8.46::gentoo'`.
 * The complete build log is located at '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220626-210052.log.gz'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/build.log.gz'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/environment'.
 * Working directory: '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/empty'
 * S: '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5'
Comment 9 João Santos 2022-07-24 08:28:40 UTC
(In reply to korte from comment #8)
> cd $(portageq get_repo_path / gentoo)
> cd app-text/master-pdf-editor
> wget https://850064.bugs.gentoo.org/attachment.cgi?id=787763 -O
> master-pdf-editor-5.8.46.ebuild
> ekeyword ~arm64 master-pdf-editor-5.8.46.ebuild
> ebuild master-pdf-editor-5.8.46.ebuild manifest
> emerge -va =app-text/master-pdf-editor-5.8.46
> 
>  * Package:    app-text/master-pdf-editor-5.8.46
>  * Repository: gentoo
>  * Maintainer: joaompssantos@gmail.com proxy-maint@gentoo.org
>  * USE:        arm64 elibc_glibc kernel_linux userland_GNU
>  * FEATURES:   ccache network-sandbox preserve-libs sandbox userpriv
> usersandbox
> >>> Unpacking source...
> >>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work
> >>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source prepared.
> >>> Configuring source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source configured.
> >>> Compiling source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source compiled.
> >>> Test phase [not enabled]: app-text/master-pdf-editor-5.8.46
>  * ERROR: app-text/master-pdf-editor-5.8.46::gentoo failed (install phase):
>  *   The source directory
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-
> 5' doesn't exist
>  *
>  * Call stack:
>  *            ebuild.sh, line  770:  Called __ebuild_main 'install'
>  *   phase-functions.sh, line 1059:  Called __dyn_install
>  *   phase-functions.sh, line  577:  Called die
>  * The specific snippet of code:
>  *              die "The source directory '${S}' doesn't exist"
>  *
>  * If you need support, post the output of `emerge --info
> '=app-text/master-pdf-editor-5.8.46::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=app-text/master-pdf-editor-5.8.46::gentoo'`.
>  * The complete build log is located at
> '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220626-210052.
> log.gz'.
>  * For convenience, a symlink to the build log is located at
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/build.log.gz'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/environment'.
>  * Working directory:
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/empty'
>  * S:
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5'

This does not happen to me in amd64, what are the contents of the temporary folder after extracting the file?

If I do "ebuild master-pdf-editor-5.8.46.ebuild prepare" and then list the folder contents I get:

ll /tmp/portage/app-text/master-pdf-editor-5.8.46/work/
total 0
drwxr-xr-x 6 portage portage 200 Dec 13  2021 master-pdf-editor-5/

Is this command "ekeyword ~arm64 master-pdf-editor-5.8.46.ebuild" required? I am not familiar with it...
Comment 10 korte 2022-07-28 06:55:19 UTC
> Is this command "ekeyword ~arm64 master-pdf-editor-5.8.46.ebuild" required? I am not familiar with it...
I am not sure, I think it tags the version as keyworded with ~arm64. Since "grep master /etc/portage/package.accept_keywords"
app-text/master-pdf-editor * ~*

exists it shoudln't be needed.

I used the steps from https://bugs.gentoo.org/850064#c8 and replaced the emerge with ebuild...

ebuild master-pdf-editor-5.8.46.ebuild prepare
>>> Existing ${T}/environment for 'master-pdf-editor-5.8.46' will be
>>> sourced. Run 'clean' to start with a fresh environment.
>>> WORKDIR is up-to-date, keeping...
 * checking ebuild checksums ;-) ...                                                               [ ok ]
 * checking miscfile checksums ;-) ...                                                             [ ok ]
>>> It appears that 'setup' has already executed for 'master-pdf-editor-5.8.46'; skipping.
>>> Remove '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/.setuped' to force setup.
>>> It appears that 'unpack' has already executed for 'master-pdf-editor-5.8.46'; skipping.
>>> Remove '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/.unpacked' to force unpack.
>>> It appears that 'prepare' has already executed for 'master-pdf-editor-5.8.46'; skipping.
>>> Remove '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/.prepared' to force prepare.

ls -l /tmp/portage/app-text/master-pdf-editor-5.8.46/work/
ls: cannot access '/tmp/portage/app-text/master-pdf-editor-5.8.46/work/': No such file or directory

rm /var/tmp/portage/app-text/master-pdf-editor-5.8.46/.setuped
rm /var/tmp/portage/app-text/master-pdf-editor-5.8.46/.unpacked
rm /var/tmp/portage/app-text/master-pdf-editor-5.8.46/.prepared

ebuild master-pdf-editor-5.8.46.ebuild prepare
>>> Existing ${T}/environment for 'master-pdf-editor-5.8.46' will be
>>> sourced. Run 'clean' to start with a fresh environment.
>>> Not marked as unpacked; recreating WORKDIR...
 * checking ebuild checksums ;-) ...                                                                                                                                                                                                                                                                                    [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                                                                                                                                                                  [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work
>>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source prepared.

ls -l /tmp/portage/app-text/master-pdf-editor-5.8.46
ls: cannot access '/tmp/portage/app-text/master-pdf-editor-5.8.46': No such file or directory

ls -l /var/tmp/portage/app-text/master-pdf-editor-5.8.46/
total 16
drwxr-xr-x 2 root    portage 4096 Jul 28 08:47 distdir
lrwxrwxrwx 1 root    root      53 Jul 28 08:47 files -> /var/db/repos/gentoo/app-text/master-pdf-editor/files
drwxr-xr-x 2 portage portage 4096 Jul 28 08:47 homedir
drwxr-xr-x 3 portage portage 4096 Jul 28 08:47 temp
drwx------ 2 portage portage 4096 Jul 28 08:47 work

 ls -l /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/
total 0
ls -l /var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/
total 48
lrwxrwxrwx 1 portage portage    79 Jul 28 08:47 build.log.gz -> /var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220728-064711.log.gz
-rw-rw-r-- 1 portage portage  1092 Jul 28 08:47 eclass-debug.log
-rw-rw-r-- 1 portage portage 34746 Jul 28 08:47 environment
drwxr-xr-x 2 portage portage  4096 Jul 28 08:47 logging
Comment 11 korte 2022-07-28 07:18:05 UTC
emerge -va =app-text/master-pdf-editor-5.8.46

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     UD~] app-text/master-pdf-editor-5.8.46::gentoo [5.8.52::gentoo] 0 KiB

Total: 1 package (1 downgrade), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No]

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-text/master-pdf-editor-5.8.46::gentoo
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work
>>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
>>> Source compiled.
>>> Test phase [not enabled]: app-text/master-pdf-editor-5.8.46
 * ERROR: app-text/master-pdf-editor-5.8.46::gentoo failed (install phase):
 *   The source directory '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5' do
esn't exist
 *
 * Call stack:
 *            ebuild.sh, line  770:  Called __ebuild_main 'install'
 *   phase-functions.sh, line 1059:  Called __dyn_install
 *   phase-functions.sh, line  577:  Called die
 * The specific snippet of code:
 *              die "The source directory '${S}' doesn't exist"
 *
 * If you need support, post the output of `emerge --info '=app-text/master-pdf-editor-5.8.46::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-text/master-pdf-editor-5.8.46::gentoo'`.
 * The complete build log is located at '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220728
-071629.log.gz'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-text/master-pdf-editor-
5.8.46/temp/build.log.gz'.
 * The ebuild environment file is located at '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/envi
ronment'.
 * Working directory: '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/empty'
 * S: '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5'

>>> Failed to emerge app-text/master-pdf-editor-5.8.46, Log file:

>>>  '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220728-071629.log.gz'
Comment 12 João Santos 2022-07-31 08:44:29 UTC
(In reply to korte from comment #11)
> emerge -va =app-text/master-pdf-editor-5.8.46
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild     UD~] app-text/master-pdf-editor-5.8.46::gentoo [5.8.52::gentoo]
> 0 KiB
> 
> Total: 1 package (1 downgrade), Size of downloads: 0 KiB
> 
> Would you like to merge these packages? [Yes/No]
> 
> >>> Verifying ebuild manifests
> 
> >>> Emerging (1 of 1) app-text/master-pdf-editor-5.8.46::gentoo
> >>> Unpacking source...
> >>> Source unpacked in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work
> >>> Preparing source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source prepared.
> >>> Configuring source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source configured.
> >>> Compiling source in /var/tmp/portage/app-text/master-pdf-editor-5.8.46/work ...
> >>> Source compiled.
> >>> Test phase [not enabled]: app-text/master-pdf-editor-5.8.46
>  * ERROR: app-text/master-pdf-editor-5.8.46::gentoo failed (install phase):
>  *   The source directory
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-
> 5' do
> esn't exist
>  *
>  * Call stack:
>  *            ebuild.sh, line  770:  Called __ebuild_main 'install'
>  *   phase-functions.sh, line 1059:  Called __dyn_install
>  *   phase-functions.sh, line  577:  Called die
>  * The specific snippet of code:
>  *              die "The source directory '${S}' doesn't exist"
>  *
>  * If you need support, post the output of `emerge --info
> '=app-text/master-pdf-editor-5.8.46::gentoo'`,
>  * the complete build log and the output of `emerge -pqv
> '=app-text/master-pdf-editor-5.8.46::gentoo'`.
>  * The complete build log is located at
> '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220728
> -071629.log.gz'.
>  * For convenience, a symlink to the build log is located at
> '/var/tmp/portage/app-text/master-pdf-editor-
> 5.8.46/temp/build.log.gz'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/temp/envi
> ronment'.
>  * Working directory:
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/empty'
>  * S:
> '/var/tmp/portage/app-text/master-pdf-editor-5.8.46/work/master-pdf-editor-5'
> 
> >>> Failed to emerge app-text/master-pdf-editor-5.8.46, Log file:
> 
> >>>  '/var/log/portage/build/app-text/master-pdf-editor-5.8.46:20220728-071629.log.gz'

Why is it downgrading? What is the previous installed version and how did you managed to do it in arm64?
Comment 13 korte 2022-07-31 09:23:33 UTC
(In reply to João Santos from comment #12)
> Why is it downgrading? What is the previous installed version and how did
> you managed to do it in arm64?

(In reply to korte from comment #0)
> I installed app-text/master-pdf-editor-5.8.52 on arm64 (Pi400) and get: 
> 

grep master /etc/portage/package.accept_keywords
app-text/master-pdf-editor * ~*
pi400 ~ # emerge -va =app-text/master-pdf-editor-5.8.52

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   *] app-text/master-pdf-editor-5.8.52::gentoo  0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] n

Quitting.

I installed it, but it doesn't work.
Comment 14 João Santos 2022-07-31 09:53:25 UTC
(In reply to korte from comment #13)
> (In reply to João Santos from comment #12)
> > Why is it downgrading? What is the previous installed version and how did
> > you managed to do it in arm64?
> 
> (In reply to korte from comment #0)
> > I installed app-text/master-pdf-editor-5.8.52 on arm64 (Pi400) and get: 
> > 
> 
> grep master /etc/portage/package.accept_keywords
> app-text/master-pdf-editor * ~*
> pi400 ~ # emerge -va =app-text/master-pdf-editor-5.8.52
> 
> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> [ebuild   R   *] app-text/master-pdf-editor-5.8.52::gentoo  0 KiB
> 
> Total: 1 package (1 reinstall), Size of downloads: 0 KiB
> 
> Would you like to merge these packages? [Yes/No] n
> 
> Quitting.
> 
> I installed it, but it doesn't work.

I don't understand how this 5.8.52 amd64 version can be installed while the arm64 version gives problems. I check the downloaded files for both architectures and they have essentially the same file structure...

Furthermore, when I replaced the amd64 link with the arm64 link it installed without flaw in my amd64 system (although I cannot run it obviously).

So... as I don't have an arm64 (are you sure it is arm64 and not some other variant?) platform to test this I am no sure how to help you any further.

Please let me know if you have any ideas.