Re: Power-up cc --print-file-name for .so names

2022-02-20 Thread Theo de Raadt
Christian Weisgerber wrote: > Mark Kettenis: > > > There is a scenario where this goes wrong. If a shared library lacks > > a DT_SONAME entry, the library filename is used to generate the > > DT_NEEDED entries. But I would consider such a shared library broken > > and we fixed base a lng t

Re: Power-up cc --print-file-name for .so names

2022-02-20 Thread Christian Weisgerber
Mark Kettenis: > There is a scenario where this goes wrong. If a shared library lacks > a DT_SONAME entry, the library filename is used to generate the > DT_NEEDED entries. But I would consider such a shared library broken > and we fixed base a lng time ago. Some care has to be taken when >

Re: Power-up cc --print-file-name for .so names

2022-02-14 Thread Theo de Raadt
Mark Kettenis wrote: > > From: "Theo de Raadt" > > Date: Mon, 14 Feb 2022 00:34:53 -0700 > > > > > The solution would be to add symlinks like all the other OSes do. But > > > Theo doesn't like that. > > > > No, the problem is you add symbolic links, how long before software > > ecosystems in

Re: Power-up cc --print-file-name for .so names

2022-02-14 Thread Theo de Raadt
Mark Kettenis wrote: > > From: Philip Guenther > > Date: Sun, 13 Feb 2022 23:29:06 -0800 > > > > On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis > > wrote: > > > > > From: Greg Steuck > > > Date: Sun, 13 Feb 2022 22:37:13 -0800 > > > > > > To give a sense of the kind of change required t

Re: Power-up cc --print-file-name for .so names

2022-02-14 Thread Mark Kettenis
> From: "Theo de Raadt" > Date: Mon, 14 Feb 2022 00:34:53 -0700 > > > The solution would be to add symlinks like all the other OSes do. But > > Theo doesn't like that. > > No, the problem is you add symbolic links, how long before software > ecosystems in ports choose the short names in linkage

Re: Power-up cc --print-file-name for .so names

2022-02-14 Thread Mark Kettenis
> From: Philip Guenther > Date: Sun, 13 Feb 2022 23:29:06 -0800 > > On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis > wrote: > > > From: Greg Steuck > > Date: Sun, 13 Feb 2022 22:37:13 -0800 > > > > To give a sense of the kind of change required to get the feature I > > want, see the patc

Re: Power-up cc --print-file-name for .so names

2022-02-14 Thread Greg Steuck
"Theo de Raadt" writes: > Philip Guenther wrote: > >> On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis >> wrote: >> >> > > From: Greg Steuck >> > > Date: Sun, 13 Feb 2022 22:37:13 -0800 >> > > >> > > To give a sense of the kind of change required to get the feature I >> > > want, see the patch

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Theo de Raadt
Philip Guenther wrote: > On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis > wrote: > > > > From: Greg Steuck > > > Date: Sun, 13 Feb 2022 22:37:13 -0800 > > > > > > To give a sense of the kind of change required to get the feature I > > > want, see the patch at the end. The change in DriverUtils

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Theo de Raadt
Philip Guenther wrote: > Those of long memory will recall a hackathon where dependencies on libc > were put in place, the libm vs libc deps were changed as functions were > moved from libm to libc, and base builds completely broke. My recall is > that the diffs had to basically be unrolled to re

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Theo de Raadt
> The solution would be to add symlinks like all the other OSes do. But > Theo doesn't like that. No, the problem is you add symbolic links, how long before software ecosystems in ports choose the short names in linkage -- "because it also works"? If they do so, all the transition benefits we ha

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Philip Guenther
On Sun, Feb 13, 2022 at 11:29 PM Philip Guenther wrote: > On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis > wrote: > >> > From: Greg Steuck >> > Date: Sun, 13 Feb 2022 22:37:13 -0800 >> > >> > To give a sense of the kind of change required to get the feature I >> > want, see the patch at the end

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Greg Steuck
Mark Kettenis writes: >> From: Greg Steuck >> Date: Sun, 13 Feb 2022 22:37:13 -0800 >> >> To give a sense of the kind of change required to get the feature I >> want, see the patch at the end. The change in DriverUtils.cpp is just to >> show that the same function is hiding in there. >> >> If

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Philip Guenther
On Sun, Feb 13, 2022 at 11:18 PM Mark Kettenis wrote: > > From: Greg Steuck > > Date: Sun, 13 Feb 2022 22:37:13 -0800 > > > > To give a sense of the kind of change required to get the feature I > > want, see the patch at the end. The change in DriverUtils.cpp is just to > > show that the same fu

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Mark Kettenis
> From: Greg Steuck > Date: Sun, 13 Feb 2022 22:37:13 -0800 > > To give a sense of the kind of change required to get the feature I > want, see the patch at the end. The change in DriverUtils.cpp is just to > show that the same function is hiding in there. > > If this looks like a good direction

Re: Power-up cc --print-file-name for .so names

2022-02-13 Thread Greg Steuck
To give a sense of the kind of change required to get the feature I want, see the patch at the end. The change in DriverUtils.cpp is just to show that the same function is hiding in there. If this looks like a good direction, I can cleanup the code and maybe it could be shared, though I'm not sure