Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] cpuburn installs files that cannot be executed
Date: Wed, 28 Dec 2022 20:51:54 +0100	[thread overview]
Message-ID: <20221228195154.6QGKFbCKONWwlnDJTpLslMmRMa8i5DvFcQjZ8dAmRxI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41307@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Closed issue by sbromberger on void-packages repository

https://github.com/void-linux/void-packages/issues/41307

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.15_1 x86_64 AuthenticAMD uptodate FF

### Package(s) Affected

cpuburn-1.4a_4

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The package is supposed to install executables in the form of `burnXX` in `/usr/bin` that can be run to stress the CPU.

### Actual behaviour

```
bash-5.1# ls -l /usr/bin/burnK7
-rwxr-xr-x 1 root root 13028 Dec 25  2019 /usr/bin/burnK7
bash-5.1# /usr/bin/burnK7
bash: /usr/bin/burnK7: No such file or directory
bash-5.1# file /usr/bin/burnK7
/usr/bin/burnK7: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=034079d40556396ee48af243ce70a87e3bc048b0, stripped
```

I think it might have to do with the fact that these binaries are 32-bit?

### Steps to reproduce

1. `xbps-install cpuburn`
2. `/usr/bin/burnK7`


      reply	other threads:[~2022-12-28 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 23:09 [ISSUE] " sbromberger
2022-12-28 19:51 ` leahneukirchen [this message]

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=20221228195154.6QGKFbCKONWwlnDJTpLslMmRMa8i5DvFcQjZ8dAmRxI@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).