all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "reza.housseini@gmail.com" <reza.housseini@gmail.com>
Cc: guix-devel@gnu.org, 66262@debbugs.gnu.org
Subject: [bug#66262] Failed to build in QA
Date: Fri, 06 Oct 2023 13:14:58 +0100	[thread overview]
Message-ID: <87zg0weyde.fsf@cbaines.net> (raw)
In-Reply-To: <FDFE0A4D-3301-427F-A7D5-225BD55BD225@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]


"reza.housseini@gmail.com" <reza.housseini@gmail.com> writes:

> On October 5, 2023 10:49:06 AM GMT+02:00, Christopher Baines <mail@cbaines.net> wrote:
>>
>>"reza.housseini@gmail.com" <reza.housseini@gmail.com> writes:
>>
>>> I submitted an issue to guix. But QA refuses to build it [1]. I have
>>> no clue what the problem is, can anyone shed light on a possible
>>> resolution?
>>
>>You pretty much found the problem, the relevant line on the page you
>>linked to is:
>>
>>[  6/ 50] loading...	 24.0% of 25 filesbuilder for `/gnu/store/qhvpjfn3d9cwz5zxadblbnbqa92a8i27-guix-cli-core.drv' failed due to signal 11 (Segmentation fault)
>>
>>So the data service wasn't able to build Guix. This probably isn't due
>>to your changes, and it doesn't happen very often, so the thing to do
>>here is just retry.
>>
>>I've triggered QA to reapply the patches now (by deleting the
>>issue-66262 branch), so hopefully things will work better this time.
>>
>>Thanks,
>>
>>Chris
>
> Thanks very much, it seems to have worked, but now it's stuck with
> paraview undefined symbol, although the necessary module
> (gnu/packages/image-processing) is imported?

This is probably down to a top level circular dependency. In particular,
trying to paraview to compute the version to form part of the
native-search-path at the top level causes problems.

Making openfoam have LD_LIBRARY_PATH as a search path seems like the
incorrect use of search paths though, since you're searching for
something in the same package. Replacing this with wrapping would be an
improvement, although still I'm unsure why LD_LIBRARY_PATH would need
setting in this case.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-10-06 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  7:43 Failed to build in QA reza.housseini
2023-10-05  8:49 ` Christopher Baines
2023-10-05 10:59   ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-10-06  5:49   ` reza.housseini
2023-10-06 12:14     ` Christopher Baines [this message]
2023-10-09 12:40       ` Reza Housseini
2023-10-09 12:40         ` [bug#66262] " Reza Housseini
2023-10-10 17:09         ` Christopher Baines
2023-10-20  7:57         ` reza.housseini
2023-10-20  7:57           ` [bug#66262] " reza.housseini
2023-11-29 14:49           ` Reza Housseini
2023-11-29 14:49             ` [bug#66262] " Reza Housseini
2023-11-29 16:06             ` Christopher Baines
2023-11-29 16:35               ` reza.housseini
2023-11-29 19:54                 ` Attila Lendvai
     [not found]                   ` <297eed25-b272-7445-5f4b-27a2a0b5deab@housseini.me>
2023-11-29 20:11                     ` [bug#66262] " reza via Guix-patches via
     [not found]                       ` <fe1cd8a5-afc2-80f3-9917-37cd57625de1@housseini.me>
2023-11-30  9:07                         ` reza via Guix-patches via

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=87zg0weyde.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=66262@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=reza.housseini@gmail.com \
    /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.