From: Ritesh Raj Sarraf <rrs@debian.org>
To: Sjoerd Simons <sjoerd@debian.org>, 928924@bugs.debian.org
Cc: linux-um@lists.infradead.org
Subject: Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
Date: Mon, 06 Jan 2020 21:51:36 +0530 [thread overview]
Message-ID: <95a2a1cdb323633a0779acaeb0377ed60e7e3afc.camel@debian.org> (raw)
In-Reply-To: <157830351172.48768.9073767232890169518.reportbug@beast>
[-- Attachment #1.1: Type: text/plain, Size: 2265 bytes --]
Control: tag -1 +help
On Mon, 2020-01-06 at 10:38 +0100, Sjoerd Simons wrote:
> On my sid system:
> ```
> $ strings /usr/bin/linux.uml | grep port-helper
> /usr/lib//uml/port-helper
> ```
>
> So the path is still incorrect even with newer upstream kernels.
I spent some time today looking at the new build but I haven't been
able to ascertain why this isn't setting the correct path.
```
$ strings `which linux.uml` | grep port-helper
/usr/lib/uml/port-helper
```
First, for context to the readers here, the port-helper binary is
shipped with uml-utilities package. This package, depending on the
architecture, installs the binary to a architecture specific location.
https://sources.debian.org/src/uml-utilities/20070815.2-1/Makefile/#L10
Which on an amd64 machine is: /usr/lib64/uml/port-helper
```
$ dpkg -S /usr/lib64/uml/port-helper
uml-utilities: /usr/lib64/uml/port-helper
```
The UML setup on my box always worked because long back, when I first
encountered this problem, I had created a symlink of the path to
/usr/lib/ too. And had completely forgotten about it. My apologies.
But that said, the current problem is with the UML binary built by the
kernel sources.
Problem is that, as mentioned above and other reports too on this bug
report thread, the path resolved at build time is always
"/usr/lib/uml/".
The build configuration and the code are all correct.
```
$ grep 64BIT .config
CONFIG_64BIT=y
CONFIG_64BIT_TIME=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
```
Snipped from: arch/um/include/shared/os.h
```
#ifdef CONFIG_64BIT
#define OS_LIB_PATH "/usr/lib64/"
#else
#define OS_LIB_PATH "/usr/lib/"
#endif
```
I also checked the generated include headers and they are correct for
the amd64 .config file.
```
linux-source-5.4/include/generated$ grep 64BIT autoconf.h
#define CONFIG_64BIT_TIME 1
#define CONFIG_PHYS_ADDR_T_64BIT 1
#define CONFIG_64BIT 1
#define CONFIG_ARCH_DMA_ADDR_T_64BIT 1
```
I'll keep looking as time permits but if anyone else has ideas on what
I may be doing wrong, please do mention.
Thanks,
Ritesh
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next parent reply other threads:[~2020-01-06 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <451d491044af46fe1d87d10196e24e8e7b076f26.camel@debian.org>
[not found] ` <157830351172.48768.9073767232890169518.reportbug@beast>
2020-01-06 16:21 ` Ritesh Raj Sarraf [this message]
2020-01-06 16:58 ` Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper Anton Ivanov
2020-01-06 17:30 ` Ritesh Raj Sarraf
2020-01-09 9:58 ` Sjoerd Simons
2020-01-06 17:25 ` Ritesh Raj Sarraf
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=95a2a1cdb323633a0779acaeb0377ed60e7e3afc.camel@debian.org \
--to=rrs@debian.org \
--cc=928924@bugs.debian.org \
--cc=linux-um@lists.infradead.org \
--cc=sjoerd@debian.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.