From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Aw: Re: Re: Re: Recompilation problems opencv (python3-cv2 --> python3.8)
Date: Fri, 15 Jan 2021 12:08:10 +0100 [thread overview]
Message-ID: <37aa8145-3c4a-4192-9ece-14178690d343@gmail.com> (raw)
In-Reply-To: <87ft32bhlp.fsf@Otto.invalid>
On 15.01.2021 11:49, ASSI wrote:
> Marco Atzeri via Cygwin writes:
>> I see this as first error
>>
>> /pub/devel/opencv/opencv-3.4.1-3.x86_64/src/opencv-3.4.1/modules/python/src2/cv2.cpp:889:34:
>> error: invalid conversion from ‘const char*’ to ‘char*’ [-fpermissive]
>> it seems the compilers is less tolerant than before.
>> It does not seem a specific python issue.
>>
>> I will see to patch it and continue when I found a bit of time
>
> What the error message is trying to tell you is that you need the
> "-fpermissive" option to CXXFLAGS if you expect the code to compile
> despite the mismatched types. Whether it will succeed or just stop
> someplace else remains to be seen.
of course
>
> The upstream package is at version 4 already, which probably needs other
> patches as a quick look at Fedora seems to indicate:
>
> https://src.fedoraproject.org/rpms/opencv/tree/master
one step at time
> Regards,
> Achim.
next prev parent reply other threads:[~2021-01-15 11:08 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 [this message]
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=37aa8145-3c4a-4192-9ece-14178690d343@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).