From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Aw: Re: Recompilation problems opencv (python3-cv2 --> python3.8)
Date: Thu, 14 Jan 2021 11:06:58 +0100 [thread overview]
Message-ID: <1a53ec30-813c-8158-89ab-1381b2608f67@gmail.com> (raw)
In-Reply-To: <trinity-edfd126c-c1fd-48fd-aa8f-c627a14c6f6e-1610618375127@3c-app-webde-bap28>
bottom reply here please
On 14.01.2021 10:59, wilhelm-eger--- via Cygwin wrote:
> Dear Csaba,
>
> Thank you for you reply.
>
> However, it does not seem to work. I have tried several things. Based on this post:
>
> https://stackoverflow.com/questions/38296756/what-is-the-idiomatic-way-in-cmake-to-add-the-fpic-compiler-option
>
> I have added -DENABLE_PIC=ON to the cmake command of the cygport file from the git repository. Further, I have tried -DCMAKE_POSITION_INDEPENDENT_CODE=ON without success. Finally, I have tried to add -fPIC to the respective compilation commands in the build.ninja file for ittnotify and the linker command without any success.
>
> This seems to be odd, as neither the cygport file nor the source code could have changed since this package has been compiled the last time for python36.
>
> (And yes, I have searched the web for the respective phrase)
>
> Any other hint? Thanks in advance.
>
> Wilhelm
I will look on current source
https://cygwin.com/packages/summary/python3-cv2.html
to see if there is a need of adjustment for Python 3.8
Do not expect immediate feedback.
Marco
next prev parent reply other threads:[~2021-01-14 10:07 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 [this message]
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
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=1a53ec30-813c-8158-89ab-1381b2608f67@gmail.com \
--to=marco.atzeri@gmail.com \
--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).