public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Recompilation problems opencv (python3-cv2 --> python3.8)
Date: Fri, 15 Jan 2021 10:14:57 -0700	[thread overview]
Message-ID: <4a922112-b721-029c-1012-03116786c502@SystematicSw.ab.ca> (raw)
In-Reply-To: <trinity-073f36c0-9f83-4e29-87fd-bd0e50003af6-1610698428037@3c-app-webde-bap59>

On 2021-01-15 01:13, wilhelm-eger--- via Cygwin wrote:
> 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?

Check your email host location:

$ geoiplookup web.de
GeoIP Country Edition: DE, Germany
GeoIP City Edition, Rev 1: DE, 01, Baden-Wurttemberg, Karlsruhe, 76137, 
49.001900, 8.428700, 0, 0
GeoIP ASNum Edition: AS8560 1&1 Internet SE

Check Cygwin German mirror locations for one nearby:

$ sed '/^\s\+[^;]\+;\([^;]\+\);Europe;Germany$/!d;s!!\1!' /etc/setup/setup.rc | 
sort -u | xargs -l1 geoiplookup
...
$ geoiplookup ftp-stud.hs-esslingen.de
GeoIP Country Edition: DE, Germany
GeoIP City Edition, Rev 1: DE, 01, Baden-Wurttemberg, Stuttgart, 70173, 
48.766701, 9.183300, 0, 0
GeoIP ASNum Edition: AS553 Universitaet Stuttgart
...

in same Land, lat/long diff about .25/.75, and about 61km great circle distance.

Find mirror URLs:

$ fgrep esslingen.de /etc/setup/setup.rc
 
ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/;ftp-stud.hs-esslingen.de;Europe;Germany
 
http://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/;ftp-stud.hs-esslingen.de;Europe;Germany
 
https://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/;ftp-stud.hs-esslingen.de;Europe;Germany

Find source package:

$ grep -m1 '^source:\s.*opencv' ~/mirror/x86_64/setup.ini
source: x86_64/release/opencv/opencv-3.4.1-2-src.tar.xz 138322784 
8da273070a232773d522dfe9b2cf098115e34a595a3d0c968b7fc0ba4f17f92db4f405857157f72f5218e17e6694c1d93ddc22c70fc6bcbf383077499373657a

Download source package:

$ curl -OJRSs 
https://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_64/release/opencv/opencv-3.4.1-2-src.tar.xz
*OR*
$ wget -N -nv 
https://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/x86_64/release/opencv/opencv-3.4.1-2-src.tar.xz

$ tar -xf opencv-3.4.1-2-src.tar.xz

Also package *patches* visible from:

https://build.opensuse.org/package/show/openSUSE:Factory/opencv3

but patches directly downloadbale from:

https://github.com/bmwiedemann/openSUSE/tree/20201007/packages/o/opencv3

[thanks to Achim for pointers]

and

https://sources.debian.org/data/main/o/opencv/3.2.0+dfsg-6/debian/patches/
https://salsa.debian.org/science-team/opencv/-/tree/debian/3.2.0+dfsg-6/debian/patches
https://salsa.debian.org/science-team/opencv/-/tree/debian/3.3.0+dfsg-1_exp0/debian/patches
https://salsa.debian.org/science-team/opencv/-/tree/debian/3.4.4+dfsg-1_exp1/debian/patches
https://salsa.debian.org/science-team/opencv/-/tree/debian/3.4.5+dfsg-1_exp1/debian/patches

and

https://src.fedoraproject.org/rpms/opencv/tree/f30

and you can pick later branches or tags for patches for later versions as you 
need from these repos: cygport can use URLs or local file names in 
PATCH_URI="..." and the string content may be a separate line per patch, usually 
with a leading tab.

> 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.
First check your current packages, toolchains, and libraries against a known 
good working set of vanilla sources at an earlier version that should have no 
issues, then work your way up to newer versions adding difficulties! ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      parent reply	other threads:[~2021-01-15 17:14 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           ` Aw: " wilhelm-eger
2021-01-15  9:34             ` 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 [this message]

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=4a922112-b721-029c-1012-03116786c502@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).