From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Jack Hill <jackhill@jackhill.us>
Cc: 37680@debbugs.gnu.org
Subject: bug#37680: simple-scan builds with newer version
Date: Thu, 10 Oct 2019 21:45:40 +0200 [thread overview]
Message-ID: <20191010214540.76d12fb8@alma-ubu> (raw)
In-Reply-To: <alpine.DEB.2.20.1910101247280.7762@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
Hi Jack,
thanks for looking into this.
On Thu, 10 Oct 2019 13:22:50 -0400 (EDT)
Jack Hill <jackhill@jackhill.us> wrote:
> The version of simple-scan that current in Guix, 3.24.1, which fails
> to build is a little old. I tried to update it to the version that
> numerically matches our GNOME version, 3.30.2, but that fails with
> the same problem.
>
> However, the current newest simple-scan release, 3.34.1, does build.
> Unfortunately, I had to take the colord out of inputs or native
> inputs otherwise the build would fail with
I was also quickly trying out the same things you did and came to the
same conclusion. I hoped to find a way around today, but I don't know
the meson-build-system and have no futher idea.
[..]
> A bigger problem than colord though, is that while simple-scan now
> builds, it doesn't run. It exits after printing "Trace/breakpoint
> trap". I've attached strace output.
Oh, sounds bad. I haven't tried to run it.
> I'm not sure what's next, thoughts?
No.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-10-10 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 10:57 bug#37680: [core-updates] simple-scan fails to build Björn Höfling
2019-10-10 17:22 ` bug#37680: simple-scan builds with newer version Jack Hill
2019-10-10 19:45 ` Björn Höfling [this message]
2019-10-10 17:23 ` bug#37680: [PATCH] gnu: simple-scan: Update to 3.34.1 Jack Hill
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=20191010214540.76d12fb8@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=37680@debbugs.gnu.org \
--cc=jackhill@jackhill.us \
/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.