SRC_URI = "
http://ftp.gnome.org/pub/GNOME/sources/gtkmm/${PV}/gtkmm-${PV}.0.tar.bz2";
S = "${WORKDIR}/${BPN}-${PV}.0"
Just rename the recipe to gtkmm_3.0.0.bb, use ${BPN}-${PV}.tar.bz2, and
delete the S assignment.
That likely won't fix your problem but can't hurt. Setting PR=r0 isn't
needed as that should be the default.
Ross
On 18 November 2016 at 16:06, Edward Vidal <devel...@sbcglobal.net> wrote:
> Hello All,
>
> Thanks to Piotr Lewicki who noticed
> package version (PV) is "3.0-r0=" and not
> "3.0-r0" ?? Maybe this "=" sign causes some problem.
> There were 2 occurrences and 7 without the "="
> /poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-
> linux-gnueabi/gtkmm/3.0-r0=/usr
>
> He recommended that I add PR = "r0" to the recipe.
> The log indicates
> arm-poky-linux-gnueabi-libtool: warning: library
> '/home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/
> sysroots/raspberrypi2/usr/lib/libatkmm-1.6.la' was moved.
> arm-poky-linux-gnueabi-libtool:
> error: cannot find the library '/usr/lib/libatk-1.0.la' or unhandled
> argument '=/usr/lib/libatk-1.0.la'
>
> Makefile:748: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/vidal/wkg/yocto/
> RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-
> poky-linux-gnueabi/gtkmm/3.0-r0/build'
> Makefile:534: recipe for target 'all' failed
> make: *** [all] Error 2
>
> Thanks in advance.
>
> Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613
>
>
> On Friday, November 18, 2016 8:04 AM, "yocto-requ...@yoctoproject.org" <
> yocto-requ...@yoctoproject.org> wrote:
>
>
> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. raspberry pi gtkmm_3.0.bb (Edward Vidal)
> 2. Re: populate_sdk_ext: Unable to locate package
> nativesdk-buildtools-perl-dummy (Paul Eggleton)
> 3. uninative vs. BB_NO_NETWORK (Vuille, Martin (Martin))
> 4. Re: undefined references to `__dso_handle' (Daniel.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 17 Nov 2016 21:01:33 +0000 (UTC)
> From: Edward Vidal <devel...@sbcglobal.net>
> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: [yocto] raspberry pi gtkmm_3.0.bb
> Message-ID: <1211982120.2332029.1479416493...@mail.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello All,
> I working with software that needs gtkmm_3.0.
> Poky 2.2 provides gtkmm_2.24.3 in
> meta-oe/reipes-gnome/gtk+
> I used recipetool and created gtkmm_3.0.bb
> I modified some lines and was able to get the
> recipe to fetch, unpack, and configure.
> when it tries to compile I am getting errors.
>
> Makefile:748: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/vidal/wkg/yocto/
> RaspberryPi2/poky/build/tmp/work/cortexa7hf-neon-vfpv4-
> poky-linux-gnueabi/gtkmm/3.0-r0/build'
> Makefile:534: recipe for target 'all' failed
> make: *** [all] Error 2
> ERROR: Function failed: do_compile (log file is located at
> /home/vidal/wkg/yocto/RaspberryPi2/poky/build/tmp/
> work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/gtkmm/3.0-
> r0/temp/log.do_compile.17760)
>
> The recipe that I am trying to create is
> https://gist.github.com/develone/ffa79327ccd49e9aa9f5c07e4db9ad7d
>
> Any an all help is appreciated.
>
> Thanks in advance ?Edward Vidal Jr. e-mail devel...@sbcglobal.net
> 915-595-1613
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/
> attachments/20161117/e682ad6a/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 18 Nov 2016 14:46:07 +1300
> From: Paul Eggleton <paul.eggle...@linux.intel.com>
> To: Michel D'HOOGE <michel.dho...@free.fr>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] populate_sdk_ext: Unable to locate package
> nativesdk-buildtools-perl-dummy
> Message-ID: <4182204.zx1rafn...@peggleto-mobl.ger.corp.intel.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Michel,
>
> On Wed, 16 Nov 2016 11:48:21 Michel D'HOOGE wrote:
> > I try to produce an extensible SDK for core-image-sato with the following
> > configuration:
> >
> > BB_VERSION = "1.32.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "universal"
> > TARGET_SYS = "x86_64-poky-linux"
> > MACHINE = "vtc7200"
> > DISTRO = "poky-systemd"
> > DISTRO_VERSION = "2.2"
> > TUNE_FEATURES = "m64 corei7"
> >
> > The machine is based on an intel-corei7, with some features removed. And
> the
> > distro is poky-based, with only systemd (as detailed in the ref manual).
> > And I get the following error:
> >
> >
> > ERROR : buildtools-tarball-1.0-r0 do_populate_sdk: Unable to install
> > packages. Command '/mnt/Yocto/vedecom-x86/build/tmp/sysroots/x86_
> > 64-linux/usr/bin/apt-get install --force-yes --allow-unauthenticated
> > nativesdk-locale-base-en-us nativesdk-git nativesdk-make native
> > sdk-ca-certificates nativesdk-tar nativesdk-python3-modules
> > nativesdk-texinfo nativesdk-python3-git nativesdk-ncurses-terminfo-base
> n
> > ativesdk-chrpath nativesdk-python3-misc nativesdk-git-perltools
> > nativesdk-buildtools-perl-dummy nativesdk-pigz nativesdk-wget natives
> > dk-python3-core' returned 100:
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> > E: Unable to locate package nativesdk-buildtools-perl-dummy
> >
> > The package exists and is in:
> > tmp/deploy/deb/buildtools-dummy-nativesdk/nativesdk-
> buildtools-perl-dummy_1.
> > 0-r2_allarch.deb while the other listed packages are in
> > tmp/deploy/deb/x86_64-nativesdk.
> >
> > It seems this package is empty, so maybe I should simply remove it from
> > poky/meta/recipes-core/meta/buildtools-tarball.bb.
>
> FYI the purpose of this package is to take precedence over the real
> nativesdk-
> perl so that it doesn't get into the buildtools, since we prefer to avoid
> the
> issues associated with overriding the host perl there. If you remove this
> package then perl will enter buildtools and you will experience other
> issues.
>
> I think the issue is this hasn't really been tested with deb packaging.
> You
> have hit a genuine bug though - would you mind filing a bug at
> http://bugzilla.yoctoproject.org?
>
> Thanks,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 18 Nov 2016 14:58:04 +0000
> From: "Vuille, Martin (Martin)" <vmar...@avaya.com>
> To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: [yocto] uninative vs. BB_NO_NETWORK
> Message-ID:
> <30C2D590D16A5C46ADFE6521910377987FF82A5C@AZ-US1EXMB02.
> global.avaya.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Currently using Yocto 1.8, planning upgrade to 2.2
>
> Per the Reference Manual, "The uninative class is now enabled by default
> in Poky. [...]
> With this class enabled, a tarball containing a pre-built C library is
> downloaded at the start of the build."
>
> We have to build with BB_NO_NETWORK = "1"
>
> How will this interact with uninative? Do we have to download the
> pre-built C library
> to our local mirror, like other package tarballs?
>
> MV
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 18 Nov 2016 13:00:45 -0200
> From: "Daniel." <danielhi...@gmail.com>
> Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
> Subject: Re: [yocto] undefined references to `__dso_handle'
> Message-ID:
> <caf3sda4kaw53kxou73b3gb+hylclqaj2wptg3bdekzwxl5h...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> Did you have multilib installed!?
>
> Regards,
>
> 2016-11-17 15:27 GMT-02:00 Elazar Leibovich <elaz...@gmail.com>:
>
> > As far as I know, no customization, I didn't even switch GCC's version.
> I
> > installed clang alongside gcc, but didn't change the default.
> >
> > Can you refer me to what you have in mind that might be customized, and
> > I'll check?
> >
> > On Thu, Nov 17, 2016 at 7:23 PM, Khem Raj <raj.k...@gmail.com> wrote:
> >
> >>
> >>
> >> On 11/16/16 2:05 AM, Elazar Leibovich wrote:
> >> > Hi,
> >> >
> >> > I followed the quickstart tutorial, branch morty, to create the most
> >> basic
> >> > image on local QEMU, and I got compilation errors for __dso_handle
> >> missing.
> >> > I'm using ubuntu 16.
> >> > Here is an example output:
> >> > ++ -nostdlib++ -fPIC -DPIC -D_GLIBCXX_SHARED -shared -nostdlib
> >> > /media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib/crti.o
> >> > /media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib/arm-poky-linux-gnueabi/6.2.0/crtbeginS.o
> >> > .libs/compatibility.o .libs/compatibility-debug_list.o
> >> > .libs/compatibility-debug_list-2.o .libs/compatibility-c++0x.o
> >> > .libs/compatibility-atomic-c++0x.o .libs/compatibility-thread-c++0x.o
> >> > .libs/compatibility-chrono.o .libs/compatibility-condvar.o
> >> > -Wl,--whole-archive ../libsupc++/.libs/libsupc++convenience.a
> >> > ../src/c++98/.libs/libc++98convenience.a
> >> > ../src/c++11/.libs/libc++11convenience.a -Wl,--no-whole-archive -lm
> >> > -L/media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> x86_64-linux/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-
> >> linux-gnueabi/6.2.0
> >> > -L/media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/lib
> >> > -L/media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib/arm-poky-linux-gnueabi/6.2.0
> >> > -L/media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib
> >> > -lc -lgcc_s
> >> > /media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib/arm-poky-linux-gnueabi/6.2.0/crtendS.o
> >> > /media/elazar/788854CC88548B10/poky/build/tmp/sysroots/
> >> raspberrypi3/usr/lib/crtn.o
> >> > -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard
> -mcpu=cortex-a7
> >> > -Wl,-O1 -Wl,-z -Wl,relro -Wl,--gc-sections -Wl,-O1
> -Wl,--hash-style=gnu
> >> > -Wl,--as-needed -Wl,--version-script=libstdc++-symbols.ver
> >> -Wl,-soname
> >> > -Wl,libstdc++.so.6 -o .libs/libstdc++.so.6.0.22
> >> > | .libs/compatibility-c++0x.o: In function
> >> > `__static_initialization_and_destruction_0':
> >> > |
> >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky
> >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi
> >> /libstdc++-v3/src/../../../../../../../../../work-shared/
> >> gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++11/
> compatibility-c++0x.cc:215:
> >> > undefined reference to `__dso_handle'
> >> > | ../src/c++11/.libs/libc++11convenience.a(system_error.o): In
> function
> >> > `__static_initialization_and_destruction_0':
> >> > |
> >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky
> >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi
> >> /libstdc++-v3/src/c++11/../../../../../../../../../../work-
> >> shared/gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++11/system_
> error.cc:71:
> >> > undefined reference to `__dso_handle'
> >> > | ../src/c++98/.libs/libc++98convenience.a(mt_allocator.o): In
> function
> >> > `get_freelist':
> >> > |
> >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky
> >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi
> >> /libstdc++-v3/src/c++98/../../../../../../../../../../work-
> >> shared/gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++98/mt_
> allocator.cc:64:
> >> > undefined reference to `__dso_handle'
> >> > | ../src/c++98/.libs/libc++98convenience.a(c++locale.o): In function
> >> > `std::get_catalogs()':
> >> > |
> >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky
> >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi
> >> /libstdc++-v3/src/c++98/c++locale.cc:251:
> >> > undefined reference to `__dso_handle'
> >> > | ../src/c++11/.libs/libc++11convenience.a(condition_variable.o): In
> >> function
> >> > `key_init':
> >> > |
> >> > /usr/src/debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky
> >> -linux-gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi
> >> /libstdc++-v3/src/c++11/../../../../../../../../../../work-
> >> shared/gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++11/
> >> condition_variable.cc:133:
> >> > undefined reference to `__dso_handle'
> >> > |
> >> > ../src/c++11/.libs/libc++11convenience.a(future.o):/usr/src/
> >> debug/gcc-runtime/6.2.0-r0/gcc-6.2.0/build.arm-poky-linux
> >> -gnueabi.arm-poky-linux-gnueabi/arm-poky-linux-gnueabi/
> >> libstdc++-v3/src/c++11/../../../../../../../../../../work-
> >> shared/gcc-6.2.0-r0/gcc-6.2.0/libstdc++-v3/src/c++11/future.cc:64:
> >> > more undefined references to `__dso_handle' follow
> >> > | collect2: error: ld returned 1 exit status
> >> >
> >> > I'll be happy for help, haven't found similar error when searching the
> >> web
> >>
> >> is it pristine ubuntu 16.04 or do you have any customization, new
> >> packages etc
> >> installed on top
> >>
> >> >
> >> >
> >>
> >>
> >
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> >
>
>
> --
> *"Do or do not. There is no try"*
> *Yoda Master*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.yoctoproject.org/pipermail/yocto/
> attachments/20161118/f9a3c7ad/attachment.html>
>
> ------------------------------
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 74, Issue 77
> *************************************
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
