all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 42667@debbugs.gnu.org
Subject: bug#42667: opencv fails to build
Date: Tue, 11 Aug 2020 00:10:54 +0200	[thread overview]
Message-ID: <20200811001054.50d1d32d@alma-ubu> (raw)
In-Reply-To: <87a6zd77o7.fsf@yamatai>

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

On Sun, 02 Aug 2020 10:50:48 +0200
Guillaume Le Vaillant <glv@posteo.net> wrote:

> When trying to build the opencv package , I get the following error:
> 
> --8<---------------cut here---------------start------------->8---
[..]
> error: lvalue required as unary ‘&’ operand jas_seqent_t* pix_row =
> &jas_matrix_get( buffer, y / ystep, 0 );

I have a patch based on this not yet released commit:

From f66fc199a20882c546fa31142e9c0f5a8b3cf983 Mon Sep 17 00:00:00 2001
From: Florian Jung <flo@windfis.ch>
Date: Wed, 29 Jul 2020 18:51:55 +0200
Subject: [PATCH] Fix build of grfmt_jpeg2000.cpp

The first round was successful, now the second run of --rounds=2 is
compiling/testing. Give me some days to clean it up and to update to the
latest 3.x release. Note: I stay with the 3.x branch as updating to 4.x
is more complicated: We need to check compatibility with existing
dependencies and there is a lot of new code which needs to be checked
for license issues.

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-08-10 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02  8:50 bug#42667: opencv fails to build Guillaume Le Vaillant
2020-08-10 22:10 ` Björn Höfling [this message]
2020-10-03  8:15 ` 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=20200811001054.50d1d32d@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=42667@debbugs.gnu.org \
    --cc=glv@posteo.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.