Can't find guile-2.0
I'm bitbaking a console image for an Atom, which worked when I did a plain vanilla version. Now I've added the OpenEmbedded layer containing Samba, and it's failing on one thing. The error message points me to a 5000-line log file called build/tmp/work/i686-linux/autogen-native-5.12-r3/temp/log.do_configure.5923, and it seems to be getting errors looking for Guile. The configure script says this:
configure:14911: checking for LIBGUILE configure:14918: $PKG_CONFIG --exists --print-errors "guile-2.0" Package guile-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `guile-2.0.pc' to the PKG_CONFIG_PATH environment variable
No package 'guile-2.0' found
and then finishes up with this:
configure:14966: error: Package requirements (guile-2.0) were not met:
No package 'guile-2.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBGUILE_CFLAGS and LIBGUILE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I used apt-get to install guile-2.0. There is a file called /usr/lib/libguile-2.0.so.22 (not sure what the .22 means), so it looks like I have the library. However, there is no .pc file for it in /usr/lib/pkgconfig, or anywhere else that I can see. I'm new to Linux, so I don't know if this is an improperly installed library or what. Anyone have any insight?
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 7 lines · Paul D. DeRocco
I'm bitbaking a console image for an Atom, which worked when I did a plain vanilla version. Now I've added the OpenEmbedded layer containing Samba, and it's failing on one thing. The error message points me to a 5000-line log file called build/tmp/work/i686-linux/autogen-native-5.12-r3/temp/log.do_configure.5923, and it seems to be getting errors looking for Guile. The configure script says this:
autogen-native should be building guile-native, you won't need the host guile. Can you confirm that by running "bitbake guile-native"?
Ross
Quoted 4 lines
From: Burton, Ross
autogen-native should be building guile-native, you won't need the host guile. Can you confirm that by running "bitbake guile-native"?
It says "attempted 145 tasks of which 145 didn't need to be rerun". So it thinks it's already there.
Or is it now confused by the fact that I installed a version with apt-get? I had gotten the same error message about the missing guile both before and after installing it with apt-get, yet apt-get did in fact download and install something.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Hi Paul,
Quoted 2 lines · Paul D. DeRocco
It says "attempted 145 tasks of which 145 didn't need to be rerun". So it thinks it's already there.
Indeed. Something is breaking - you'll have to mail the whole
configure log from autogen to attempt to debug this.
Quoted 4 lines
Or is it now confused by the fact that I installed a version with apt-get? I had gotten the same error message about the missing guile both before and after installing it with apt-get, yet apt-get did in fact download and install something.
Apt would have installed a guile into /usr. I'm a bit surprised that it didn't find that either. Try "bitbake pkgconfig-native" and then "bitbake autogen-native", maybe we've found a bootstrap bug.
Ross
Quoted 9 lines
From: Burton, Ross
Quoted 2 lines · Paul D. DeRocco
It says "attempted 145 tasks of which 145 didn't need to be rerun". So it thinks it's already there.
Indeed. Something is breaking - you'll have to mail the whole
configure log from autogen to attempt to debug this.
One thing that I notice is that in my build/tmp/work/i686-linux, I have two directories, autogen-native-5.12-r2 and autogen-native-5.12-r3. The first is from my successful out-of-the-box build of a week ago; the second is from my current failed build. What I did in between was to add the openembedded-core/meta and meta-openembedded/meta-oe layers in order to include Samba. The two logs deviate at line 275 where the old successful one says "checking whether with-libguile was specified... no" and the new failed one says "checking for i686-linux-pkg-config... no". I suspect something in the OE stuff appended to a recipe, which is leading to the problem.
Quoted 10 lines
Quoted 6 lines
Or is it now confused by the fact that I installed a version with apt-get? I
had gotten the same error message about the missing guile both before and
after installing it with apt-get, yet apt-get did in fact download and install something.Apt would have installed a guile into /usr. I'm a bit surprised that it didn't find that either. Try "bitbake pkgconfig-native" and then "bitbake autogen-native", maybe we've found a bootstrap bug.
Yes, apt-get put it into /usr, but there's no .pc file for it.
When I bitbaked pkgconfig-native, it was a no-op. Then, when I bitbaked autogen-native, I got the usual error again. I also tried removing the version of guile that I had with apt-get, and bitbaking guile-2.0 was still a no-op, and bitbaking autogen-native still produced the error.
Also, even though bitbaking guile-2.0 was a no-op, there is no guile command available, since I uninstalled the version I had. Or does that recipe just produce the library, and not the executable?
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 10 lines · Paul D. DeRocco
Quoted 9 lines
From: Burton, Ross
Quoted 2 lines · Paul D. DeRocco
It says "attempted 145 tasks of which 145 didn't need to be rerun". So it thinks it's already there.
Indeed. Something is breaking - you'll have to mail the whole
configure log from autogen to attempt to debug this.
Quoted 10 lines
One thing that I notice is that in my build/tmp/work/i686-linux, I have two directories, autogen-native-5.12-r2 and autogen-native-5.12-r3. The first is from my successful out-of-the-box build of a week ago; the second is from my current failed build. What I did in between was to add the openembedded-core/meta and meta-openembedded/meta-oe layers in order to include Samba. The two logs deviate at line 275 where the old successful one says "checking whether with-libguile was specified... no" and the new failed one says "checking for i686-linux-pkg-config... no". I suspect something in the OE stuff appended to a recipe, which is leading to the problem.
Same thing here. Everything was building fine until I added the meta-oe layer.
Does one of you have a workaround for this?
Thanks,
Marc
Quoted 9 lines · Paul D. DeRocco
One thing that I notice is that in my build/tmp/work/i686-linux, I have two directories, autogen-native-5.12-r2 and autogen-native-5.12-r3. The first is from my successful out-of-the-box build of a week ago; the second is from my current failed build. What I did in between was to add the openembedded-core/meta and meta-openembedded/meta-oe layers in order to include Samba. The two logs deviate at line 275 where the old successful one says "checking whether with-libguile was specified... no" and the new failed one says "checking for i686-linux-pkg-config... no". I suspect something in the OE stuff appended to a recipe, which is leading to the problem.
The old sucessful one worked more through luck than anything else, -r3 was introduced to fix this.
Using current master I just confirmed this works for me.
checking for x86_64-linux-pkg-config... no
checking for pkg-config... /data/poky-master/tmp/sysroots/x86_64-linux/usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBGUILE... yes
checking for x86_64-linux-pkg-config... /data/poky-master/tmp/sysroots/x86_64-linux/usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking the guile version... 2.0.7
In your log the pkgconfig checks are succeeding, it's the guile check that fails:
checking for pkg-config... /home/pauld/yocto-atom/build/tmp/sysroots/i686-linux/usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBGUILE... no
configure: error: Package requirements (guile-2.0) were not met:
No package 'guile-2.0' found
autogen-native depends on guile-native so that should have worked - try doing "bitbake -ccleansstate guile-native ; bitbake guile-native" to force that to be rebuilt.
Ross
Quoted 5 lines
From: Burton, Ross
autogen-native depends on guile-native so that should have worked - try doing "bitbake -ccleansstate guile-native ; bitbake guile-native" to force that to be rebuilt.
It complains that guile-native doesn't have a task called do_cleanstate.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 7 lines · Paul D. DeRocco
Quoted 5 lines
From: Burton, Ross
autogen-native depends on guile-native so that should have worked - try doing "bitbake -ccleansstate guile-native ; bitbake guile-native" to force that to be rebuilt.
It complains that guile-native doesn't have a task called
do_cleanstate.
Yep, so it should, I was wrong. Try bitbake -f guile-native. The dependencies say that you should have guile-native already, so I don't know why it would be failing.
Ross
Quoted 5 lines
From: Burton, Ross
Yep, so it should, I was wrong. Try bitbake -f guile-native. The dependencies say that you should have guile-native already, so I don't know why it would be failing.
That "worked", in the sense of claiming to have executed the do_build task, but it happened so fast that I think all it did was run a null make. When I then did a bitbake of the entire image, I got the same error I got before, about not being able to find guile-2.0. Is there some manual surgery I can perform on the tree to get rid of the guile that it thinks exists, and really force it to be remade?
By the way, when I do "bitbake -s", it lists both guile AND guile-native as being version 1.8.7-r1.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 6 lines · Paul D. DeRocco
That "worked", in the sense of claiming to have executed the
do_buildtask, but it happened so fast that I think all it did was run a null make. When I then did a bitbake of the entire image, I got the same error I got before, about not being able to find guile-2.0. Is there some manual surgery I can perform on the tree to get rid of the guile that it thinks exists, and really force it to be remade?
Okay, try doing "bitbake -c devshell autogen-native", and then running "pkg-config --cflags --libs guile-2.0". That should produce errors, which may be more useful. Debugging over email is quite difficult. :(
Ross
Quoted 5 lines
From: Burton, Ross
Okay, try doing "bitbake -c devshell autogen-native", and then running "pkg-config --cflags --libs guile-2.0". That should produce errors, which may be more useful. Debugging over email is quite difficult. :(
It complains that guile-2.0 is not found in the pkg-config search path, and suggests adding the directory containing guile-2.0.pc to PKG_CONFIG_PATH. This variable contains two directories within my build directory:
tmp/sysroots/i686-linux/usr/lib/pkgconfig tmp/sysroots/i686-linux/usr/share/pkgconfig
The first directory contains guile-1.8.pc, not guile-2.0.pc.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 6 lines · Paul D. DeRocco
Quoted 5 lines
From: Burton, Ross
Okay, try doing "bitbake -c devshell autogen-native", and then running "pkg-config --cflags --libs guile-2.0". That should produce errors, which may be more useful. Debugging over email is quite difficult. :(
Quoted 8 lines
It complains that guile-2.0 is not found in the pkg-config search path, and suggests adding the directory containing guile-2.0.pc to
PKG_CONFIG_PATH. This variable contains two directories within my build directory:tmp/sysroots/i686-linux/usr/lib/pkgconfig
tmp/sysroots/i686-linux/usr/share/pkgconfigThe first directory contains guile-1.8.pc, not guile-2.0.pc.
Okaaaay. So what version of oe-core or poky are you using that is providing the guile-native? Having autogen-native r3 implies some revision of master post-danny, as danny (1.3) only has autogen-native r2. Either way, both Danny and master have guile-native 2.0.6.
What are you exact layers and versions? I'm not understanding why you're not getting the guile-native that must be present alongside your autogen-native (as I fixed guile and then fixed autogen in the same day).
Ross
Quoted 7 lines
From: Ross Burton
Okaaaay. So what version of oe-core or poky are you using that is providing the guile-native? Having autogen-native r3 implies some revision of master post-danny, as danny (1.3) only has autogen-native r2. Either way, both Danny and master have guile-native 2.0.6.
They're both current within the last few weeks. However, a bit of history:
My goal was to add Samba, which is contained in the meta-oe layer of meta-openembedded, which also required adding the meta layer of openembedded-core. But I initially used the master branch, got errors, and someone else told me I needed to use the danny branch. So it is possible that something is lying around from when I first tried the master branch.
Quoted 4 lines
What are you exact layers and versions? I'm not understanding why you're not getting the guile-native that must be present alongside your autogen-native (as I fixed guile and then fixed autogen in the same day).
My layers are
poky-danny-8.0/meta
poky-danny-8.0/meta-yocto
poky-danny-8.0/meta-yocto-bsp
poky-danny-8.0/meta-intel
poky-danny-8.0/meta-intel/meta-cedartrail
poky-danny-8.0/openembedded-core/meta
poky-danny-8.0/meta-openembedded/meta-oe
where the last two are not part of poky-danny-8.0, but were fetched separately from OpenEmbedded's git server, and the rest came from a couple of tarballs from the Yocto site. I'm not sure how to find specific version info on these, but like I said, they're all from the last few weeks.
Do I need to clean something out, or should I nuke the build tree and start over, now that I've got the right OE branch?
By the way, since you're from Intel, why the hell are they discontinuing the Atom D2700?
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 6 lines · Paul D. DeRocco
They're both current within the last few weeks. However, a bit of history:
My goal was to add Samba, which is contained in the meta-oe layer of meta-openembedded, which also required adding the meta layer of openembedded-core. But I initially used the master branch, got errors, and someone else told me I needed to use the danny branch. So it is possible that something is lying around from when I first tried the master branch.
Right. Probably easiest to blow away your tmp/ as it will have bits of master in, and downgrading isn't supported.
Quoted 2 lines
By the way, since you're from Intel, why the hell are they discontinuing the Atom D2700?
Wish I knew… Cedar Trail wasn't great, but it's certainly better than waiting for Valleyview. That's the hardware group, nothing to do with me! :)
Ross
Quoted 5 lines
From: Ross Burton
Right. Probably easiest to blow away your tmp/ as it will have bits of master in, and downgrading isn't supported.
Quoted 1 line
By the way, since you're from Intel, why the hell are they
Okay, here goes...
I'll let you know how it comes out, some time tomorrow. I'm compiling it on my lowly D2700. ;-)
Thanks for your help.
Quoted 3 lines
Wish I knew. Cedar Trail wasn't great, but it's certainly better than waiting for Valleyview. That's the hardware group, nothing to do with me! :)
The D2700 has been great for my synthesizer project. Plenty of SSE horsepower with no fan. I'll have to switch to the N2800, but that just means somewhat fewer voices.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Quoted 4 lines · Paul D. DeRocco
Okay, here goes...
I'll let you know how it comes out, some time tomorrow. I'm compiling it on my lowly D2700. ;-)
Oh my!
If you wiped tmp/ but left sstate/, it shouldn't take that long.
Ross
Still no joy. Nuked tmp/, re-checkedout the current danny branch head on both meta-openembedded and openembedded-core, and got the same error. Here are some things I notice about what's in my directory trees:
My build tree shows both guile-1.8.7 and guile-2.0.6 in downloads. It shows stuff related to both guile-native-1.8.7 and guile-native-2.0.6 in sstate-cache. It only shows guile-native-1.8.7 elsewhere in the build tree. I also see two copies of guile-1.8.pc. It therefore looks like bitbake is only doing a native build of guile-1.8.7.
In the metadata trees, meta-openembedded/meta-oe has recipes called "guile_1.8.7.bb" and "guile-native_1.8.7.bb". poky-danny-8.0/meta and openembedded-core/meta both have recipes called "guile_2.0.6.bb". The latter has some extra junk in it I don't understand. Nothing has a recipe called "guile-native_2.0.6.bb".
So let me see if I understand the problem. Everything worked fine when I built the standard image, but I started having problems when I pulled in a couple of repositories from OpenEmbedded so that I could add a Samba server. Something in the layers I added needs to run a tool called autogen, so it tries to do a native build of autogen-5.12-r3. In the process of configuring that, it needs access to guile-2.0.6, but it can't find it, so it quits. Is it looking to run guile, or is it looking for a native version of the guile library to link into autogen? Somehow, I've got the source for this version of guile, but nothing is building it, and there is no recipe for it. Where is the recipe supposed to be found? Or is this simply a tool that I'm supposed to have on my machine in the first place, and bitbake doesn't try to build it?
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Hi Paul,
Quoted 5 lines · Paul D. DeRocco
In the metadata trees, meta-openembedded/meta-oe has recipes called "guile_1.8.7.bb" and "guile-native_1.8.7.bb". poky-danny-8.0/meta and openembedded-core/meta both have recipes called "guile_2.0.6.bb". The latter has some extra junk in it I don't understand. Nothing has a recipe called "guile-native_2.0.6.bb".
Ah ha!
poky contains a copy of oe-core, so you don't need both, for a given version the meta/ directories will be identical (poky is the union of oe-core, bitbake, and meta-yocto).
I'd forgotten that meta-oe used to have guile in. Presumably the problem here is that autogen-native wants guile-native and it finds guile-native_1.8.7 before realising that guile_2.0.7 can also do a native build (that's what BBCLASSEXTEND=native does).
Try using BBMASK to hide the guile in meta-oe. Add this to your local.conf:
BBMASK = "meta-oe/recipes-support/guile"
Quoted 4 lines
So let me see if I understand the problem. Everything worked fine when I built the standard image, but I started having problems when I pulled in a couple of repositories from OpenEmbedded so that I could add a Samba server. Something in the layers I added needs to run a tool called autogen, so it
Quoted 8 lines
tries to do a native build of autogen-5.12-r3. In the process of configuring that, it needs access to guile-2.0.6, but it can't find it, so it quits. Is it looking to run guile, or is it looking for a native version of the guile library to link into autogen? Somehow, I've got the source for this version of guile, but nothing is building it, and there is no recipe for it. Where is the recipe supposed to be found? Or is this simply a tool that I'm supposed to have on my machine in the first place, and bitbake doesn't try to build it?
The root cause is normally needing to build grub. grub needs autogen-native which needs guile-native, as it uses guile. We don't assume guile exists on the host, so will always build it ourselves.
Normally guile_2.0.6.bb can do both cross and native builds. It appears that meta-oe has an older version of guile with an explicit guile-native name, which is selected before the newer version in oe-core. This is the root of the problem, and the BBMASK should cause it to ignore that recipe. I've just submitted a patch to remove this guile from meta-oe, as it's just causing trouble.
Ross
Quoted 13 lines
From: Burton, Ross
Ah ha!
poky contains a copy of oe-core, so you don't need both, for a given version the meta/ directories will be identical (poky is the union of oe-core, bitbake, and meta-yocto).
I'd forgotten that meta-oe used to have guile in. Presumably the problem here is that autogen-native wants guile-native and it finds guile-native_1.8.7 before realising that guile_2.0.7 can also do a native build (that's what BBCLASSEXTEND=native does).
Quoted 4 lines
Try using BBMASK to hide the guile in meta-oe. Add this to your local.conf:
BBMASK = "meta-oe/recipes-support/guile"
That did it. However, I think we've been chasing floobydust, due to a cockpit error on my part. The reason I was including openembedded-core/meta is because it defined fontcache.bbclass, which meta-openembedded/meta-oe referred to. But that was only true when I was erroneously using the master branches of their git repositories. Now that I'm on the danny branches, I see that that isn't a problem any more. So I've removed openembedded-core/meta entirely from my bblayers.conf, and I'm trying a rebuild now, and will let you know the results.
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]
Actually, I did need the BBMASK so the problem was real. But I didn't need to include the openembedded-core/meta layer.
Thanks so much for your help. Now to go on to find the next set of problems...
Signature · 2 lines
Ciao, Paul D. DeRocco Paul mailto:[email protected]