all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "reza.housseini@gmail.com" <reza.housseini@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, 66262@debbugs.gnu.org
Subject: Re: Failed to build in QA
Date: Fri, 20 Oct 2023 07:57:44 +0000	[thread overview]
Message-ID: <DBFF3BC7-263C-454D-83B1-303F2D864A3E@gmail.com> (raw)
In-Reply-To: <2c3bb152-6928-cdcd-a8b6-593218a6d4e9@gmail.com>

On October 9, 2023 12:40:40 PM UTC, Reza Housseini <reza.housseini@gmail.com> wrote:
>> 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.
>
>I'm wondering why it builds fine locally but causes problems in QA have you any pointers what might be the difference?
>
>> 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
>Hmm maybe you are right, will try to wrap the binaries instead...

I removed the search-path but it still fails to build, I cannot make sense of the error message...


WARNING: multiple messages have this Message-ID (diff)
From: "reza.housseini@gmail.com" <reza.housseini@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, 66262@debbugs.gnu.org
Subject: [bug#66262] Failed to build in QA
Date: Fri, 20 Oct 2023 07:57:44 +0000	[thread overview]
Message-ID: <DBFF3BC7-263C-454D-83B1-303F2D864A3E@gmail.com> (raw)
Message-ID: <20231020075744.QeSWtg59pEbxlD1OKRUjCqnuDLlJtN9m0nGswJMWPwI@z> (raw)
In-Reply-To: <2c3bb152-6928-cdcd-a8b6-593218a6d4e9@gmail.com>

On October 9, 2023 12:40:40 PM UTC, Reza Housseini <reza.housseini@gmail.com> wrote:
>> 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.
>
>I'm wondering why it builds fine locally but causes problems in QA have you any pointers what might be the difference?
>
>> 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
>Hmm maybe you are right, will try to wrap the binaries instead...

I removed the search-path but it still fails to build, I cannot make sense of the error message...




  parent reply	other threads:[~2023-10-20  7:58 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     ` [bug#66262] " Christopher Baines
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 [this message]
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=DBFF3BC7-263C-454D-83B1-303F2D864A3E@gmail.com \
    --to=reza.housseini@gmail.com \
    --cc=66262@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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.