all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vinicius Monego <monego@posteo.net>
To: Brice Waegeneire <brice@waegenei.re>, bdju <bdju@tilde.team>
Cc: 49161@debbugs.gnu.org
Subject: bug#49161: kicad-5.1.6 fails to build
Date: Tue, 22 Jun 2021 09:42:07 +0000	[thread overview]
Message-ID: <c3127d8dd310a4ff48e44369c94dd1367a079176.camel@posteo.net> (raw)
In-Reply-To: <87fsxawgl1.fsf@waegenei.re>

Hi,

I found suggestions that disabling --with-readline in libngspice should
work around the issue, though I couldn't test it yet. This seems to be
a problem in version 34 specifically. Downgrading to 33 could also
work.

Em ter, 2021-06-22 às 08:36 +0200, Brice Waegeneire escreveu:
> Hello bdju,
> 
> Cuirass can't manage to build kicad¹ also.  Comparing to the previous
> build², libngspice has been updated from version 28 to 34³ and the
> content of thoses 2 version are drasticly different, so I guess it's
> the
> issue.  In particular the /gnu/store/...-libngspice-
> 34/include/config.h
> seems suspicious.
> 
> I tried bumping kicad to the latest 5.10, but it didn't make a
> difference.
> 
> ¹ https://ci.guix.gnu.org/build/608393/details
> ² https://ci.guix.gnu.org/build/608201/details
> ³ https://issues.guix.gnu.org/48979
> 
> Cheers,
> - Brice






  reply	other threads:[~2021-06-22  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 16:23 bug#49161: kicad-5.1.6 fails to build bdju via Bug reports for GNU Guix
2021-06-22  6:36 ` Brice Waegeneire
2021-06-22  9:42   ` Vinicius Monego [this message]
2021-06-22  9:42   ` Vinicius Monego
2021-06-22 11:04   ` Vinicius Monego
2021-06-22 12:01     ` Guillaume Le Vaillant
2021-06-22 13:29       ` Vinicius Monego
2021-06-22 13:39       ` Vinicius Monego
2021-06-22 14:54         ` Guillaume Le Vaillant

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=c3127d8dd310a4ff48e44369c94dd1367a079176.camel@posteo.net \
    --to=monego@posteo.net \
    --cc=49161@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    --cc=brice@waegenei.re \
    /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.