From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Serial line lock directory
Date: Wed, 07 Jun 2017 14:32:09 +0200 [thread overview]
Message-ID: <87o9u03rna.fsf@gnu.org> (raw)
In-Reply-To: <87a85kuvv6.fsf@gmail.com> (Chris Marusich's message of "Tue, 06 Jun 2017 23:58:53 -0700")
Chris Marusich <cmmarusich@gmail.com> skribis:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> I'm trying to package minicom and there I get an error message
>>
>> checking for com line lock directory... configure: error: No suitable lock directory
>>
>> ... which was checking for a (common) directory to put a file in (as a marker) when a serial device is in use (and removing the file to free the serial device). This is supposed to prevent multiple different programs accidentally using the same serial line.
>>
>> Where and how should this be done in Guix?
>
> That sounds like a directory which should exist in the localstatedir
> (info '(standards) Directory Variables'). I haven't looked closely at
> the package, but your package definition makes it look like it's using a
> GNU build system, so hopefully it provides a way to configure the
> value used for the localstatedir.
Probably it checks whether $localstatedir exist, and it doesn’t exist in
the build environment. So you’ll have to somehow tweak ‘configure’ into
skipping that test, perhaps by setting the relevant ‘ac_cv_’ variable if
it exists.
HTH!
Ludo’.
next prev parent reply other threads:[~2017-06-07 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 18:54 Serial line lock directory Danny Milosavljevic
2017-06-07 6:58 ` Chris Marusich
2017-06-07 12:32 ` Ludovic Courtès [this message]
2017-06-08 19:08 ` Danny Milosavljevic
2017-06-09 13:50 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9u03rna.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).