all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 27894@debbugs.gnu.org
Subject: bug#27894: Building Guix fails without '/etc/services'
Date: Mon, 24 Feb 2020 17:51:28 +0100	[thread overview]
Message-ID: <87eeukhqsv.fsf@gnu.org> (raw)
In-Reply-To: <924c83ae-af91-9999-7a2e-ce43afa8d88f@web.de> (Jonathan Brielmaier's message of "Tue, 11 Feb 2020 21:50:31 +0100")

Hi,

Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:

> On 11.02.20 21:40, Julien Lepiller wrote:> This is somewhat similar to
> what happens on android, and probably any systen using an alternate
> libc. Guix uses its own libc that expects an /etc/services and other
> files. I guess a symlink from /etc to /usr/etc is all you need?.
> Yes a symlink does resolve it. But doing it on all my systems is annoying :P
>
> But I wonder how much effort would be required to make this hardcoding
> of `/etc/services` more flexible. I'm mean Tumbleweed uses glibc. The
> only thing different is that they are moving all/most of config files
> from /etc to /usr/etc for $reason.

It seems to me that this question should be addressed in glibc proper.
Perhaps glibc should provide a way to configure this.

Or is openSuSE’s libc configured with --sysconfdir=/usr/etc?

Thanks,
Ludo’.

      reply	other threads:[~2020-02-24 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  0:23 bug#27894: Building Guix fails without '/etc/services' Leo Famulari
2017-08-01 10:09 ` Ludovic Courtès
2017-08-01 19:39   ` Leo Famulari
2020-02-11 20:10 ` Jonathan Brielmaier
2020-02-11 20:40   ` Julien Lepiller
2020-02-11 20:50     ` Jonathan Brielmaier
2020-02-24 16:51       ` Ludovic Courtès [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=87eeukhqsv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27894@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.