[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1596009] Re: config/build problem due to libncursesw o

From: T. Huth
Subject: [Qemu-devel] [Bug 1596009] Re: config/build problem due to libncursesw on Xenial
Date: Sun, 26 Jun 2016 07:11:39 -0000

Could you please try to reproduce this problem with the latest release
of QEMU (version 2.6)? Thanks!

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  config/build problem due to libncursesw on Xenial

Status in QEMU:

Bug description:
  it happened to me during a build of yocto/bitbake related cross tools.
  the auto-configuration part titled "SDL probe" for qemu-2.2.0 i found
  the configuration step failing for the compile_prog routine. actually
  those test compile went fine but only the test linking failed.

  this was due a reference of the sub-sub-...-included libcaca
  referenced an initially not installed (hint: check for and report such
  pre-requisites upfront - might be yocto related) and later on
  installed by me component of name libncursesw seemingly in its dev
  variant (i was installing
  libncursesw5-dev_6.0+20160213-1ubuntu1_amd64.deb). tests on the
  command line showed that adding the required paths and resources made
  the test application link nicely.

  a quick hack attempt for the config script resulted in those line:
    sdl_libs="$sdl_libs -L/lib/x86_64-linux-gnu -lncursesw"
  this allowed me to pass the configuration check nicely.
  i am just seeing my full scale compile fail for the same reason multiple 
times for linking. that all should be fixable the same way.

  you might or might not have addressed this in newer versions of your
  package. but you probably know that setups for embedded targets will
  sometimes lack behind in their evolution until a sudden (well
  prepared) some big jump in versions does happen. so i leave the hint
  here for your reference - for the main reason of this very often
  spotted message - raised by several main reasons according to public
  web reports, but not this one until right here and now:

  | ERROR: User requested feature sdl
  |        configure was not able to find it.
  |        Install SDL devel

  By the way these lines already have to locations in the configure script
  where the first indicates that pkg/sdl/sdl2-config application is not there 
(=no SDL devel there)
  whilst the second indicates that *-config is there but the test compile 
failed (=devel is broken for some other reason).
  This could/should see some improvement as well as this is the first hint on 
what went wrong - and in the second case you definitely can give the user the 
quite valueable hint for the log file with the results of the test compile.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]