From: "Carlo B." <carlo.bramini@gmail.com>
To: cygwin@cygwin.com
Subject: Re: CMake support into libssh-0.8.7-1 is broken.
Date: Fri, 21 Jan 2022 21:22:22 +0100 [thread overview]
Message-ID: <CADt9577w0JHyqfO9U7D+3u+kgaZwvijrSfrMCQHpxpeW3KFFyQ@mail.gmail.com> (raw)
In-Reply-To: <01920794-91a0-19db-332c-9ec026c06fbe@gmail.com>
Hello,
Il giorno gio 20 gen 2022 alle ore 20:07 Marco Atzeri
<marco.atzeri@gmail.com> ha scritto:
>
> On 15.01.2022 14:19, Marco Atzeri wrote:
> > On 14.01.2022 23:30, Carlo B. wrote:
> >> Hello,
> >> I discovered that CMake support into current libssh-0.8.7-1 is broken.
> >> After you installed the development package, you just need to add this
> >> line into a dummy CMakeLists.txt:
> >>
> >>
> >> find_package(libssh)
> >>
> >>
>
> >>
> >> So, I downloaded the latest sources from the repository: GCC still
> >> emits an internal compiler error, but only when building the examples.
> >> So I configured with -DWITH_EXAMPLES=OFF and I got the base library
> >> compiled.
> >> Here, I verified that the macros for CMake are generated correctly
> >> with the right names and paths.
> >>
> >> Is it possible to fix or update this package?
> >> Thank you very much for your time.
> >>
> >> Sincerely.
> >>
> >
> > noted
> >
> > Regards
> > Marco
> >
>
> what´s happening if you try to use libssh2 ?
>
Thank you for the reply.
Unfortunately, I doubt that it can be possible because libssh is
required for building Codelite for CYGWIN.
About the crash of CYGWIN GCC when building the latest source of
libssh, this is caused by the "-fstack-clash-protection" option.
However, according to this issue at bugzilla for GCC:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90458
it should not be used when the target platform is Windows and derivates.
> Currently libssh is without maintainer and it is anyway obsolete
> so probably you should build with libssh2
>
This is a bad news actually, I mean the missing maintaner.
Sincerely.
prev parent reply other threads:[~2022-01-21 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 22:30 Carlo B.
2022-01-15 13:19 ` Marco Atzeri
2022-01-20 19:06 ` Marco Atzeri
2022-01-21 20:22 ` Carlo B. [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=CADt9577w0JHyqfO9U7D+3u+kgaZwvijrSfrMCQHpxpeW3KFFyQ@mail.gmail.com \
--to=carlo.bramini@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).