> But, let me flip the question around: how exactly is it *wrong* to
> include a "redundant" rpath? Technically speaking, is there a good
> reason to want to avoid explicitly baking in the rpath for default
> search paths?
I concur, but would like to add that signalling to the build a packaging
s
On Sat, Jan 29, 2022 at 12:08:17PM +0100, Sören Tempel wrote:
> I don't think there is a semi-portable way of doing this, or at least I
> am personally not aware of one. However, maybe a Makefile configuration
> variable could be introduced specifically for creating CHICKEN Scheme
> packages for a
Peter Bex wrote:
> Hi Sören,
Hi Peter,
> > I was wondering if it would be possible to only add additional rpath
> > entries if -deployed is given or non-host-mode is used. The attached
> > git-format-patch(1) implements this. Would it be possible to integrate
> > it upstream?
>
> Given what I s
On Sun, Jan 23, 2022 at 12:54:58PM +0100, Sören Tempel wrote:
> I recently started working on Alpine packages for Scheme software which
> I compiled with CHICKEN. While doing so, I noticed that csc(1)
> unconditionally adds $(LIBDIR) as an rpath entry by adding
> -Wl,-rpath=$(LIBDIR) to the linker
Hello,
I maintain a CHICKEN package for Alpine Linux. At Alpine, have a custom
tool called abuild for packaging software based on package recipes. As
part of our build process, we perform various sanity checks. One of these
sanity checks is ensuring that the packaged software doesn't contain any
r
