RE: [EXT] Re: Bugs in SSH module

[Sawyer Liu]

Hi,
        As you said, I disabled libssh(./configure --disable-libssh), but the 
result is the same as before. Cannot compile QEMU.
        Thanks. 

Best Regards
Sawyer Liu(刘维峰)

-----Original Message-----
From: Berto Furth <bertofurth@sent.com> 
Sent: Monday, January 25, 2021 19:38
To: Sawyer Liu <sawyer.liu@nxp.com>; Nerijus Baliunas 
<nerijus@users.sourceforge.net>
Cc: nerijus--- via <qemu-discuss@nongnu.org>
Subject: Re: [EXT] Re: Bugs in SSH module

Caution: EXT Email

I believe we're talking about when you run "configure" to compile QEMU from the 
source code. It's not a parameter you pass to QEMU itself.

So when you compile QEMU from the source code you first run something like...

configure --disable-libssh <and any other options you like> make

Run "configure --help" to see all the available options.

Then QEMU will compile without trying to use libssh and hopefully you'll avoid 
all those errors.

Good luck!

On Mon, 25 Jan 2021, at 20:04, Sawyer Liu wrote:
> Hello Nerijus,
>       Sorry, I am newer for QEMU, could you tell me details how to 
> config QEMU? Thanks.
>
> Best Regards
> Sawyer Liu(刘维峰)
>
> -----Original Message-----
> From: Nerijus Baliunas <nerijus@users.sourceforge.net>
> Sent: Monday, January 25, 2021 16:42
> To: Sawyer Liu <sawyer.liu@nxp.com>
> Cc: qemu-discuss@nongnu.org
> Subject: Re: [EXT] Re: Bugs in SSH module
>
> Caution: EXT Email
>
> Hi,
>
> it is written in the email you quoted:
> you can pass QEMU configure "--disable-libssh".
>
> Regards,
> Nerijus
>
> On Mon, 25 Jan 2021 02:12:25 +0000 Sawyer Liu <sawyer.liu@nxp.com> wrote:
>
> > Hello peter,
> >       How to disable libssh for QEMU? Thanks.
> >
> >
> > Best Regards
> > Sawyer Liu(Áõά·å)
> >
> > -----Original Message-----
> > From: Peter Maydell <peter.maydell@linaro.org>
> > Sent: Friday, January 22, 2021 18:23
> > To: Sawyer Liu <sawyer.liu@nxp.com>
> > Cc: qemu-discuss@nongnu.org
> > Subject: [EXT] Re: Bugs in SSH module
> >
> > Caution: EXT Email
> >
> > On Fri, 22 Jan 2021 at 03:49, Sawyer Liu <sawyer.liu@nxp.com> wrote:
> > >        I found same question, see 
> > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fqemu%2F%2Bbug%2F1838763&amp;data=04%7C01%7Csawyer.liu%40nxp.com%7Cbd58f51ce6a045a3a91708d8c125a979%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637471714790059547%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=U%2FTegU4q236nennH0mfjtEGx4mhS2DFOmdjjTcgQ584%3D&amp;reserved=0.
> > >  The status is ¡°Won¡¯t Fix¡±. Do you have any result?
> >
> > The only feature that compiling QEMU with libssh adds is support for a 
> > 'ssh' block backend. That means you can pass '-drive 
> > file=ssh://host/path/to/file' to get QEMU to open a disk image on a remote 
> > machine.
> >
> > If you don't need to use that feature, you can pass QEMU configure 
> > "--disable-libssh". QEMU will then just not try to use the Ubuntu libssh.
> >
> > There seems to be some confusion in this thread about whether the problem 
> > is libssh or libssl. These are two different libraries. The bug report you 
> > give the URL for is for libssh.
> >
> > thanks
> > -- PMM
>
>

sss.jpg
Description: sss.jpg