Re: [EXT] Re: Bugs in SSH module

[Berto Furth]

Hi Sawyer,

I'm not sure but I think I *could* be seeing the problem. In the configure log 
you're doing configure in the " ~/optee-qemu/qemu " directory

sawyer@ubuntu:~/optee-qemu/qemu$ ./configure --disable-libssh

But then in the make log you're doing make in a different directory called " 
~/optee-qemu/build "

sawyer@ubuntu:~/optee-qemu/build$ make > makelog.txt

It was my understanding that you have to run both in the same directory 
otherwise the "make" might be using configuration files generated by a 
different "configure" statement.

Can you try the following to clear out the "build" directory (or make a new 
build directory), run configure from the build directory and then run make from 
the same build directory? So for example...

sawyer@ubuntu:~/optee-qemu/build$ rm -rf *
sawyer@ubuntu:~/optee-qemu/build$ ../qemu/configure --disable-libssh
sawyer@ubuntu:~/optee-qemu/build$ make

I can confirm that on my system if I do that (using qemu-5.2.0) then the 
block/ssh.c file isn't compiled. 

If this suggestion doesn't work then I have no idea what's going on! 

Good luck!

On Wed, 27 Jan 2021, at 14:20, Sawyer Liu wrote:
> Hello Berto,
>       Please see attached files are log. I have done "make clean" before 
> "make".
>       Thanks. 
> 
> Best Regards
> Sawyer Liu(刘维峰)
> 
> -----Original Message-----
> From: Berto Furth <bertofurth@sent.com> 
> Sent: Tuesday, January 26, 2021 17:48
> 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
> 
> Can you post a text attachment of the complete build log when you do 
> "configure --disable-libssh"? Can you make sure you're doing a "make 
> clean" before recompiling?
> 
> Thanks!
> 
> On Tue, 26 Jan 2021, at 19:26, Sawyer Liu wrote:
> > 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%7Cb4cdefa4942d493f2a8308d8c1df79c0%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637472512870531714%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8JbKPHCJH9u14WdpX4qRSlROh6YOdeWuXzD6qwfajpU%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
> > >
> > >
> >
> > Attachments:
> > * sss.jpg
> 
> Attachments:
> * config_qemu.txt
> * makelog.txt
> * outputlog.txt