From: Nikita Karetnikov <nikita@karetnikov.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] distro: Add Kmod.
Date: Mon, 24 Dec 2012 14:21:46 -0500 [thread overview]
Message-ID: <877go7ntlt.fsf@karetnikov.org> (raw)
In-Reply-To: <87r4mmdy09.fsf@gnu.org> ("Ludovic Courtès"'s message of "(unknown date)")
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
>>> Can you look at the detailed build logs?
>> 'config.log' contains several errors. For instance:
>>
>> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>> compilation terminated.
>>
>> Is it important?
> That’s expected: configure tests for the presence of certain features,
> and some are missing, etc.
>> This (from 'test-depmod.c') looks suspicious:
>>
>> #define MODULES_ORDER_LIB_MODULES MODULES_ORDER_ROOTFS "/lib/modules/" MODULES_ORDER_UNAME
>>
>> (I don't know C.)
>>
>> Also, 'test-testsuite.c' contains the following:
>>
>> fp = fopen("/lib/modules/a", "r");
>>
>> fd = open("/lib/modules/a", O_RDONLY);
> Yeah, this will never work for us, because there’s no /lib.
>
> I support we’d rather ignore tests for now, with a comment explaining
> that this is kernel-dependent, and that we’ll revisit the issue when we
> have a bootable distro.
OK.
> Why do you need this, BTW? It’ll be essentially unusable at this stage
> because of the above.
'udev-182' depends on 'kmod'.
'guix-import' doesn't list 'kmod' in 'inputs' for 'udev-173'. I can try
to package it instead of 'udev-182'. It might also solve the error which
is described in the "How to adjust PKG_CONFIG_PATH?" thread.
Nikita
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-12-24 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 2:59 [PATCH] distro: Add Kmod Nikita Karetnikov
2012-12-19 12:31 ` Ludovic Courtès
2012-12-24 19:21 ` Nikita Karetnikov [this message]
2012-12-24 22:22 ` Nikita Karetnikov
2012-12-30 14:15 ` 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=877go7ntlt.fsf@karetnikov.org \
--to=nikita@karetnikov.org \
--cc=bug-guix@gnu.org \
--cc=ludo@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).