public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Manuel Jacob <me@manueljacob.de>, libc-help@sourceware.org
Subject: Re: Pass rootsbindir to configure via command line
Date: Thu, 18 May 2023 09:29:38 -0300	[thread overview]
Message-ID: <b5f23626-dca2-7d4d-2ce0-6ccdec6f4d0c@linaro.org> (raw)
In-Reply-To: <af78016d-b1b0-bec5-d474-f9db2541b2ad@manueljacob.de>



On 30/04/23 10:09, Manuel Jacob wrote:
> Hi,
> 
> I’d like to set rootsbindir. There is no option --rootsbindir. Passing rootsbindir=… to the configure script via command line has no effect. Linux From Scratch (https://www.linuxfromscratch.org/lfs/view/stable/chapter08/glibc.html) passes libc_cv_slibdir=… to set slibdir. libc_cv_rootsbindir also exists, but passing it via command line doesn’t have any effect.
> 
> I know that setting libc_cv_rootsbindir is possible via the configparms file. Is that the only way? Passing libc_cv_slibdir via command line works, so I wonder whether I missed something.

Unfortunately I think so. The --sbindir and alike option are autogenerated by
autoconf and its latest version does not seems to have support for 
--rootsbindir [1].

But I think it might make sense for split-usr configurations, although we only
install two programs using rootsdir (ldconfig and sln).

[1] https://www.gnu.org/software/autoconf/manual/autoconf-2.71/html_node/Installation-Directory-Variables.html

      reply	other threads:[~2023-05-18 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 13:09 Manuel Jacob
2023-05-18 12:29 ` Adhemerval Zanella Netto [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=b5f23626-dca2-7d4d-2ce0-6ccdec6f4d0c@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-help@sourceware.org \
    --cc=me@manueljacob.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).