public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: wilhelm-eger@web.de
To: cygwin@cygwin.com
Subject: Aw: Re:  Re: Re: Recompilation problems opencv (python3-cv2 --> python3.8)
Date: Fri, 15 Jan 2021 09:13:48 +0100	[thread overview]
Message-ID: <trinity-073f36c0-9f83-4e29-87fd-bd0e50003af6-1610698428037@3c-app-webde-bap59> (raw)
In-Reply-To: <a7624bb8-7fb5-fe0e-affc-1fc251cd916f@SystematicSw.ab.ca>

Gesendet: Donnerstag, 14. Januar 2021 um 23:52 Uhr

> Please try by downloading the complete Cygwin source package, and try a vanilla
> rebuild first with zero changes, then change only the .cygport VERSION= to the
> latest, rebuild, and fix any problems with that as you go.

I have done the following

mkdir opencv
cd opencv
git clone http://cygwin.com/git/cygwin-packages/opencv.git .
cygport opencv.cygport fetch
cygport opencv.cygport all

Same error.

Is there any other location where I could get the opencv source package from?

Btw. there is no need to change to another Version, I just want to have cv2 also in python3.8 working. From what I have experienced with this package I assume that this would also not compile with python3.6 atm. Seems to be a cmake or gcc error to me.



  reply	other threads:[~2021-01-15  8:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  7:08 wilhelm-eger
2021-01-14  8:18 ` Csaba Raduly
2021-01-14  9:59   ` Aw: " wilhelm-eger
2021-01-14 10:06     ` Marco Atzeri
2021-01-14 10:24       ` Aw: " wilhelm-eger
2021-01-14 22:52         ` Brian Inglis
2021-01-15  8:13           ` wilhelm-eger [this message]
2021-01-15  9:34             ` Aw: " Marco Atzeri
2021-01-15 10:49               ` ASSI
2021-01-15 11:08                 ` Marco Atzeri
2021-01-15 19:34                   ` Marco Atzeri
2021-01-19  8:09                     ` Aw: " wilhelm-eger
2021-01-15 17:14             ` Brian Inglis

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=trinity-073f36c0-9f83-4e29-87fd-bd0e50003af6-1610698428037@3c-app-webde-bap59 \
    --to=wilhelm-eger@web.de \
    --cc=cygwin@cygwin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).