Re: [yocto] libtool problem?
On 04/09/2013 11:24, Hans Beckérus wrote: On Wed, Sep 4, 2013 at 9:53 AM, Hans Beckérus wrote: Hi. I recently discovered that our populated SDK can not properly build much at all :( libtool complains about .la files that have been moved and not being able to find dito. The rootfs builds fine however. What I did noticed was that in our .la files we get lines like this: dependency_libs=' =/usr/lib/libxcb.la =/usr/lib/libXau.la =/usr/lib/libXdmcp.la' Is that '='-sign really supposed to be there? Is that why many builds fails to properly locate the .la files? The '='-sign is still a mystery to me. But it does not seem to matter much. If I configure my packages (built from the SDK toolchain) using '--with-libtool-sysroot=/home/toolchain/sysroots/cortexa9-vfp-poky-linux-gnueabi/' it works! But should that really be needed? Is the path to be used by libtool not supposed to be automatically resolved to point at the toolchain sysroot in cross-compilation environment? In my case '--with-libtool-sysroot' is correctly resolved by the SDK setup, but ./configure complains it does not recognize it, so I end up not being able to test generated (dynamically linked) binaries. The common "hello world" template says it cannot find ld-linux, and indeed it's in the path of libtool-sysroot. Googling it did not helped me to resolve the issue :( Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] BitBake errors when building core-image-minimal
On 04/09/2013 14:21, Thomas Page wrote:
Hi
Having installed the Yocto required packages and created a git branch
of the project in a new installation of Ubuntu 12.04 LTS I have tried
building the core-image-minimal image but continually have the process
fail. Having gone through the installation process several times not I
simply cannot seem to get this solved.
i must add that after a fresh install of the yocto project and set up
of my host i find that Bitbake will not execute on first attempt and
must be installed. I do not remember this having to be done in my
previous use of the Yocto Project to successfully build an image.
The error i get is as follows:
tpage@ubuntu:~/poky/batmel$ bitbake core-image-minimal
Traceback (most recent call last):
File "/usr/bin/bitbake", line 234, in
ret = main()
File "/usr/bin/bitbake", line 197, in main
server = ProcessServer(server_channel, event_queue, configuration)
File "/usr/lib/pymodules/python2.7/bb/server/process.py", line 78,
in __init__
self.cooker = BBCooker(configuration, self.register_idle_function)
File "/usr/lib/pymodules/python2.7/bb/cooker.py", line 76, in __init__
self.parseConfigurationFiles(self.configuration.file)
File "/usr/lib/pymodules/python2.7/bb/cooker.py", line 510, in
parseConfigurationFiles
data = _parse(os.path.join("conf", "bitbake.conf"), data)
TypeError: getVar() takes exactly 3 arguments (2 given)
ERROR: Error evaluating
'${TARGET_OS}:${TRANSLATED_TARGET_ARCH}:build-${BUILD_OS}:pn-${PN}:${MACHINEOVERRIDES}:${DISTROOVERRIDES}:${CLASSOVERRIDE}:forcevariable'
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 116, in
expandWithRefs
s = __expand_var_regexp__.sub(varparse.var_sub, s)
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 60, in
var_sub
var = self.d.getVar(key, 1)
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 260, in
getVar
return self.expand(value, var)
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 132, in
expand
return self.expandWithRefs(s, varname).value
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 117, in
expandWithRefs
s = __expand_python_regexp__.sub(varparse.python_sub, s)
TypeError: getVar() takes exactly 3 arguments (2 given)
ERROR: Error evaluating
'${@bb.parse.BBHandler.vars_from_file(d.getVar('FILE'),d)[0] or
'defaultpkgname'}'
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 117, in
expandWithRefs
s = __expand_python_regexp__.sub(varparse.python_sub, s)
File "/usr/lib/pymodules/python2.7/bb/data_smart.py", line 76, in
python_sub
value = utils.better_eval(codeobj, DataContext(self.d))
File "/usr/lib/pymodules/python2.7/bb/utils.py", line 387, in
better_eval
return eval(source, _context, locals)
File "PN", line 1, in
TypeError: getVar() takes exactly 3 arguments (2 given)
Any feedback will be appreciated even as to where I should look for
the problem
Hi Thomas
Make sure you installed all the required packages in ubuntu.
Try running with -DDD to have additional feedback or input to the list
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] raspberry layer
Hi, I am maintaining a small project based on yocto and would like to check to what extent I can port it to Raspberry. It seems there's an ongoing rapsberry layer but I couldn't find which is the right URL to point to in order to get started. Can someone tell me ? Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] adding specific config files
Hi,
In my project, we have our own rpm repository and we use smartpm on the
target.
In order to have the target setup with the repo out of the box, we of
course have added "package-management" in IMAGE_FEATURES. Now I'd like
the target to have our repo address already configured.
The best way I found was to create a recipe in my overlay and hacking
the system a little bit this way :
do_install() {
if
${@base_contains('IMAGE_FEATURES','package-management','true','false',d)};
then
install -d ${D}/${sysconfdir}
install -m 644 ${WORKDIR}/config.in ${D}/var/lib/smart/config
fi
}
where "config.in" is a simple copy of the non-human readable version of
smartpm config file, generated manually on the target.
I was wondering if there would be a better way such as do not test in
the do_install, but rather make the recipe dependent on the
"package-management" image feature ? (so that do_install wouldn't even
be considered if the option is not set), or any other smarter idea.
Thanks a lot,
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding specific config files
On 04/09/2013 20:58, JC wrote:
Hi,
In my project, we have our own rpm repository and we use smartpm on
the target.
In order to have the target setup with the repo out of the box, we of
course have added "package-management" in IMAGE_FEATURES. Now I'd like
the target to have our repo address already configured.
The best way I found was to create a recipe in my overlay and hacking
the system a little bit this way :
do_install() {
if
${@base_contains('IMAGE_FEATURES','package-management','true','false',d)};
then
install -d ${D}/${sysconfdir}
install -m 644 ${WORKDIR}/config.in ${D}/var/lib/smart/config
fi
}
where "config.in" is a simple copy of the non-human readable version
of smartpm config file, generated manually on the target.
I was wondering if there would be a better way such as do not test in
the do_install, but rather make the recipe dependent on the
"package-management" image feature ? (so that do_install wouldn't even
be considered if the option is not set), or any other smarter idea.
Actually I _need_ a better idea because mine doesn't work: it actually
creates what I want (/var/lib/smart/config) but since do_rootfs also
uses this directory to install packages, it wipes it out at the end of
the process... so my installation is removed :(
I'm sure someone else did something like this (but succeeded) ?
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding specific config files
On 04/09/2013 21:58, JC wrote:
On 04/09/2013 20:58, JC wrote:
Hi,
In my project, we have our own rpm repository and we use smartpm on
the target.
In order to have the target setup with the repo out of the box, we of
course have added "package-management" in IMAGE_FEATURES. Now I'd
like the target to have our repo address already configured.
The best way I found was to create a recipe in my overlay and hacking
the system a little bit this way :
do_install() {
if
${@base_contains('IMAGE_FEATURES','package-management','true','false',d)};
then
install -d ${D}/${sysconfdir}
install -m 644 ${WORKDIR}/config.in ${D}/var/lib/smart/config
fi
}
where "config.in" is a simple copy of the non-human readable version
of smartpm config file, generated manually on the target.
I was wondering if there would be a better way such as do not test in
the do_install, but rather make the recipe dependent on the
"package-management" image feature ? (so that do_install wouldn't
even be considered if the option is not set), or any other smarter idea.
Actually I _need_ a better idea because mine doesn't work: it actually
creates what I want (/var/lib/smart/config) but since do_rootfs also
uses this directory to install packages, it wipes it out at the end of
the process... so my installation is removed :(
I'm sure someone else did something like this (but succeeded) ?
The guilty line is in /sources/poky/meta/classes/rootfs_rpm.bbclass
145: rm -rf ${IMAGE_ROOTFS}/var/lib/smart
:(
Whatever I want to do with packages, It'll be removed. There's probably
an alternate way :(
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry layer
On 04/09/2013 18:46, Gary Thomas wrote:
On 2013-09-04 10:40, JC wrote:
Hi,
I am maintaining a small project based on yocto and would like to
check to what extent I can port it to Raspberry.
It seems there's an ongoing rapsberry layer but I couldn't find which
is the right URL to point to in order to get started.
Can someone tell me ?
git://git.yoctoproject.org/meta-raspberrypi
Thanks. I checked out everything (including a "fresh" poky) and I get
this error:
ERROR: Error executing a python function in :# | ETA: 00:00:57
ExpansionError: Failure expanding variable MAJ_VER, expression was
${@oe.utils.trim_version("2.28.2", 2)} which triggered exception
AttributeError: 'module' object has no attribute 'trim_version'
my local.conf changes: just added raspberrypi machine
bblayers.conf:
added
/media/yocto/yocto/openembedded-core/meta \
/media/yocto/yocto/meta-raspberrypi \
(i had to add meta otherwise it complained it didn't have the mesa recipe)
Any idea? Do you need the complete failure log or is this something known ?
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry layer
Hi,
On 05/09/2013 09:31, Paul Barker wrote:
That looks like a parse error so the full log shouldn't be very long
as that point, may be helpful to post it.
I attached rpibuild.log to this email
my local.conf changes: just added raspberrypi machine
bblayers.conf:
added
/media/yocto/yocto/openembedded-core/meta \
/media/yocto/yocto/meta-raspberrypi \
The README in meta-raspberrypi states that you need meta-openembedded
as well (specifically, the meta-oe layer). I'm not sure that this is
the cause of your error though.
Sorry, it is indeed added (otherwise it complains about mesa, anyway)
What branches of the different layers are you using? I just want to
make sure they're all the same. Also, what version or branch of
bitbake are you using?
As a reference, following this link
http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7 I got successful
(well the image is not yet finished but I hadn't that specific parsing
error)
I followed the exact README steps in a fresh directory for the checkout,
so I am on the trunk for poky & meta-raspberrypi...
Jay
ERROR: Error executing a python function in :# | ETA: 00:00:57
ExpansionError: Failure expanding variable MAJ_VER, expression was ${@oe.utils.trim_version("2.28.2", 2)} which triggered exception AttributeError: 'module' object has no attribute 'trim_version'
ERROR: The stack trace of python calls that resulted in this exception/failure was:
ERROR: File "", line 1, in
ERROR:
ERROR: File "__anon_637__media_yocto_yocto_poky_meta_classes_base_bbclass", line 169, in __anon_637__media_yocto_yocto_poky_meta_classes_base_bbclass
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 503, in getVar
ERROR: return self.expand(value, var)
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 336, in expand
ERROR: return self.expandWithRefs(s, varname).value
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 317, in expandWithRefs
ERROR: s = __expand_var_regexp__.sub(varparse.var_sub, s)
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 97, in var_sub
ERROR: var = self.d.getVar(key, True)
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 503, in getVar
ERROR: return self.expand(value, var)
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 336, in expand
ERROR: return self.expandWithRefs(s, varname).value
ERROR:
ERROR: File "/media/yocto/yocto/poky/bitbake/lib/bb/data_smart.py", line 326, in expandWithRefs
ERROR: raise ExpansionError(varname, s, exc)
ERROR:
ERROR: The code that was being executed was:
ERROR: *** 0001:__anon_637__media_yocto_yocto_poky_meta_classes_base_bbclass(d)
ERROR: 0002:__anon_227__media_yocto_yocto_poky_meta_classes_package_bbclass(d)
ERROR: 0003:__anon_1137__media_yocto_yocto_poky_meta_classes_package_rpm_bbclass(d)
ERROR: 0004:__anon_914__media_yocto_yocto_poky_meta_classes_insane_bbclass(d)
ERROR: 0005:__anon_20__media_yocto_yocto_poky_meta_classes_debian_bbclass(d)
ERROR: [From file: '', lineno: 1, function: ]
ERROR: 0165:elif all_skipped or incompatible_license(d, bad_licenses):
ERROR: 0166:bb.debug(1, "SKIPPING recipe %s because it's %s" % (pn, recipe_license))
ERROR: 0167:raise bb.parse.SkipPackage("incompatible with license %s" % recipe_license)
ERROR: 0168:
ERROR: *** 0169:srcuri = d.getVar('SRC_URI', True)
ERROR: 0170:# Svn packages should DEPEND on subversion-native
ERROR: 0171:if "svn://" in srcuri:
ERROR: 0172:d.appendVarFlag('do_fetch', 'depends', ' subversion-native:do_populate_sysroot')
ERROR: 0173:
ERROR: [From file: '__anon_637__media_yocto_yocto_poky_meta_classes_base_bbclass', lineno: 169, function: __anon_637__media_yocto_yocto_poky_meta_classes_base_bbclass]
ERROR: Failed to parse recipe: /media/yocto/yocto/openembedded-core/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.28.2.bb
ERROR: Command execution failed: Exited with 1
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry layer
On 05/09/2013 10:04, Paul Barker wrote:
On 5 September 2013 08:55, JC wrote:
As a reference, following this link
http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7 I got successful
(well the image is not yet finished but I hadn't that specific parsing
error)
I followed the exact README steps in a fresh directory for the checkout, so
I am on the trunk for poky & meta-raspberrypi...
The log you've attached shows paths for poky as well as
openembedded-core. Poky is basically a combination of
openembedded-core, meta-yocto and bitbake so you don't want to add
openembedded-core again. Could you post your full bblayers.conf?
Yes that's strange. Do you think it could be an issue with trunk ?
Here's my bblayers:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
/media/yocto/yocto/poky/meta-yocto-bsp \
/media/yocto/yocto/meta-openembedded/meta-oe \
/media/yocto/yocto/meta-raspberrypi \
"
BBLAYERS_NON_REMOVABLE ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry layer
In the log you posted is the line:
ERROR: Failed to parse recipe:
/media/yocto/yocto/openembedded-core/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.28.2.bb
So something was adding the path
/media/yocto/yocto/openembedded-core/meta to BBLAYERS. If you've just
removed that, give it another try.
I did remove that and gave another try *before* sending the mail :) so
some cache were present.
In order to make sure everything with fine I sourced oe-init-build-env
to a new directory
As a reminder here's how my stuff is installed:
from a directory /media/yocto/yocto I performed a git clone of poky,
meta-raspberrypi and meta-openembedded so I now have :
$ ls
meta-openembedded meta-raspberrypi poky rpi
(rpi is the name of the directory I oe-init'd)
Here are the steps:
1. local.conf is unmodified, except for MACHINE set to raspberrypi
2. bblayers.conf is:
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
/media/yocto/yocto/poky/meta-yocto-bsp \
/media/yocto/yocto/meta-openembedded/meta-oe \
/media/yocto/yocto/meta-raspberrypi \
"
BBLAYERS_NON_REMOVABLE ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
"
3. bitbake rpi-image-basic
Pseudo is not present but is required, building this first before the
main build
Loading cache: 100%
|##|
ETA: 00:00:00
Loaded 202 entries from dependency cache.
ERROR: ParseError at
/media/yocto/yocto/meta-openembedded/meta-oe/recipes-devtools/libgee/libgee.inc:12:
Could not inherit file classes/vala.bbclass
ERROR: Command execution failed: Exited with 1
If this is not something you get with a head checkout of poky,
meta-raspberrypi and meta-openembedded, I can retry a new fresh git
clone to test again...
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] raspberry layer
Hi Paul On 05/09/2013 10:28, Paul Eggleton wrote: Hi Jay, On Thursday 05 September 2013 10:20:41 JC wrote: ERROR: ParseError at /media/yocto/yocto/meta-openembedded/meta-oe/recipes-devtools/libgee/libgee. inc:12: Could not inherit file classes/vala.bbclass ERROR: Command execution failed: Exited with 1 If this is not something you get with a head checkout of poky, meta-raspberrypi and meta-openembedded, I can retry a new fresh git clone to test again... This looks to me like the branch you have checked out of meta-oe does not match up with the branch of poky. If you are using the "dylan" branch of poky you need to be using the "dylan" branch of meta-oe and meta-raspberrypi. I re-checked out all of the gits with -b dylan, now the bitbake goes further.. Let's see where/if it fails :) Thanks !!! Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding specific config files
On 05/09/2013 11:32, Paul Eggleton wrote:
Hi Jay,
On Wednesday 04 September 2013 22:10:10 JC wrote:
On 04/09/2013 21:58, JC wrote:
On 04/09/2013 20:58, JC wrote:
Hi,
In my project, we have our own rpm repository and we use smartpm on
the target.
In order to have the target setup with the repo out of the box, we of
course have added "package-management" in IMAGE_FEATURES. Now I'd
like the target to have our repo address already configured.
The best way I found was to create a recipe in my overlay and hacking
the system a little bit this way :
do_install() {
if
${@base_contains('IMAGE_FEATURES','package-management','true','false',d)}
;
then
install -d ${D}/${sysconfdir}
install -m 644 ${WORKDIR}/config.in ${D}/var/lib/smart/config
fi
}
where "config.in" is a simple copy of the non-human readable version
of smartpm config file, generated manually on the target.
I was wondering if there would be a better way such as do not test in
the do_install, but rather make the recipe dependent on the
"package-management" image feature ? (so that do_install wouldn't
even be considered if the option is not set), or any other smarter idea.
Actually I _need_ a better idea because mine doesn't work: it actually
creates what I want (/var/lib/smart/config) but since do_rootfs also
uses this directory to install packages, it wipes it out at the end of
the process... so my installation is removed :(
I'm sure someone else did something like this (but succeeded) ?
The guilty line is in /sources/poky/meta/classes/rootfs_rpm.bbclass
145: rm -rf ${IMAGE_ROOTFS}/var/lib/smart
:(
Whatever I want to do with packages, It'll be removed. There's probably
an alternate way :(
Unfortunately we have to have a fixed configuration for smart during do_rootfs,
so it has to be written to. I think though that rather than trying to install
a configuration file for smart using a separate recipe, I would suggest
modifying the smart configuration at the end of do_rootfs to add the
configuration elements you need. The way to do this would be to define a shell
function that you can add a call to in ROOTFS_POSTPROCESS_COMMAND that will
run smart:
add_extra_smart_config() {
smart --data-dir=${IMAGE_ROOTFS}/var/lib/smart channel --add rpmsys
type=rpm-sys -y
}
ROOTFS_POSTPROCESS_COMMAND += "add_extra_smart_config; "
You can put the above in the image recipe itself or in a class that your image
recipe inherits.
Cheers,
Paul
Thanks, I'm going to try it !!
Assuming I don't want to create a new image (i still haven't exactly
figured how to do this in a clean way), where should I append this code ?
How can I make it dependend on the "package-management" feature?
Thanks again,
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding specific config files
On jeu., sept. 5, 2013 at 12:00 PM, Paul Eggleton
mailto:paul.eggle...@linux.intel.com";>> wrote:
On Thursday 05 September 2013 11:45:26 JC wrote:
> On 05/09/2013 11:32, Paul Eggleton wrote:
> > Unfortunately we have to have a fixed configuration for smart during
> > do_rootfs, so it has to be written to. I think though that rather than
> > trying to install a configuration file for smart using a separate recipe,
> > I would suggest modifying the smart configuration at the end of do_rootfs
> > to add the configuration elements you need. The way to do this would be
> > to define a shell function that you can add a call to in
> > ROOTFS_POSTPROCESS_COMMAND that will run smart:
> >
> > add_extra_smart_config() {
> >
> > smart --data-dir=${IMAGE_ROOTFS}/var/lib/smart channel --add rpmsys
> > type=rpm-sys -y>
> > }
> > ROOTFS_POSTPROCESS_COMMAND += "add_extra_smart_config; "
> >
> > You can put the above in the image recipe itself or in a class that your
> > image recipe inherits.
> >
> > Cheers,
> > Paul
>
> Thanks, I'm going to try it !!
>
> Assuming I don't want to create a new image (i still haven't exactly
> figured how to do this in a clean way), where should I append this code ?
To be honest I always recommend people create their own image recipes
whatever they are doing since image recipes are usually trivial and
almost always need to be customised. The easiest way to do this is to
copy an existing image recipe and name it and modify it as you prefer.
> How can I make it dependend on the "package-management" feature?
If "package-management" is not in IMAGE_FEATURES the smart config gets deleted
anyway so this will have no effect. However, if desired you can use an inline
python expression within the shell function to do things conditionally, e.g.
if ${@base_contains("IMAGE_FEATURES", "package-management", "true", "false",
d)}; then
...
fi
It's important to realise though that the evaluation of the inline
python happens when the expression is parsed, not when the shell
function it is executed; by the time the shell function executes the
expression will have been converted to its result.
Cheers,
Paul
Thanks ! I'm gonna try and let you know !
Jay___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] (solved) Re: adding specific config files
Hi Paul
On 05/09/2013 12:00, Paul Eggleton wrote:
On Thursday 05 September 2013 11:45:26 JC wrote:
On 05/09/2013 11:32, Paul Eggleton wrote:
Unfortunately we have to have a fixed configuration for smart during
do_rootfs, so it has to be written to. I think though that rather than
trying to install a configuration file for smart using a separate recipe,
I would suggest modifying the smart configuration at the end of do_rootfs
to add the configuration elements you need. The way to do this would be
to define a shell function that you can add a call to in
ROOTFS_POSTPROCESS_COMMAND that will run smart:
add_extra_smart_config() {
smart --data-dir=${IMAGE_ROOTFS}/var/lib/smart channel --add rpmsys
type=rpm-sys -y>
}
ROOTFS_POSTPROCESS_COMMAND += "add_extra_smart_config; "
You can put the above in the image recipe itself or in a class that your
image recipe inherits.
Cheers,
Paul
Thanks, I'm going to try it !!
Assuming I don't want to create a new image (i still haven't exactly
figured how to do this in a clean way), where should I append this code ?
To be honest I always recommend people create their own image recipes
whatever they are doing since image recipes are usually trivial and
almost always need to be customised. The easiest way to do this is to
copy an existing image recipe and name it and modify it as you prefer.
How can I make it dependend on the "package-management" feature?
If "package-management" is not in IMAGE_FEATURES the smart config gets deleted
anyway so this will have no effect. However, if desired you can use an inline
python expression within the shell function to do things conditionally, e.g.
if ${@base_contains("IMAGE_FEATURES", "package-management", "true", "false",
d)}; then
...
fi
It's important to realise though that the evaluation of the inline
python happens when the expression is parsed, not when the shell
function it is executed; by the time the shell function executes the
expression will have been converted to its result.
This worked perfectly. Just a slight append : your need to "install -d"
the /var/lib/smartpm directory, otherwise it seems it's not created. Not
a big deal anyway
Thanks again !!
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] ruby-dev requires libcrypto which is not present ??
Hi, I'm trying to install ruby-dev (in order to be able to apply some passenger features). Passenger requires ruby-dev ruby-dev has indeed been built but when I'm trying to install it, I can't: root@qemuarm:~# smart install ruby-dev rpmdb: BDB0113 Thread/proc Computing transaction... error: Can't install ruby-dev-1.9.3+p194-r1.0@armv5te: no package provides libcrypto-dev And of course, libcrypto-dev is _not_ present, as smart tells me. I wonder how ruby-dev has been compiled if libcrypto is not here. Or how can I solve the issue ? How can I make sure libcryto is also generated (or not deleted?) during build process? I'm working on the qemuarm device, but I'm not sure how much the problem is bound to it or could be reproduced on other targets. Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ruby-dev has a lot of unresolved dependencies (was : requires libcrypto which is not present ??)
Hi, I auto-follow on this question: On 06/09/2013 17:51, JC wrote: I'm trying to install ruby-dev (in order to be able to apply some passenger features). Passenger requires ruby-dev ruby-dev has indeed been built but when I'm trying to install it, I can't: root@qemuarm:~# smart install ruby-dev rpmdb: BDB0113 Thread/proc Computing transaction... error: Can't install ruby-dev-1.9.3+p194-r1.0@armv5te: no package provides libcrypto-dev libcrypto-dev is not present because openssl does not generate it (it's empty, the lib is taken by libcrypto package) I hacked (may be I'll clean) it by modifying the openssl recipe allowing libcrypto-dev to be empty. Then I ran into the same error with libssl-dev so the "hack" is now : PACKAGES =+ " libcrypto-dev libssl-dev" ALLOW_EMPTY_libcrypto-dev = "1" ALLOW_EMPTY_libssl-dev = "1" Now the next error is : Computing transaction...error: Can't install ruby-dev-1.9.3+p194-r1.0@armv5te: no package provides ncurses-libtinfo-dev That one is trickier. It seems that libtinfo is provided by the package ncurses-terminfo, not ncurses-libtinfo. I'm really confused about the status of meta-ruby. I assume I'm not the only one willing to install ruby-dev am I ? Is there some basic mistake I made ? How can yocto even generate the package if it cannot satisfy these dependencies by itself ? Thanks for your help... I'm really puzzled now :( Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Any help with gst-plugsin-bad and python error?
On 08/09/2013 19:32, Timothy Bean wrote: | Computing transaction...error: Can't install libglib-2.0-utils-1:2.34.3-r2@armv7a_vfp_neon: no package provides /usr/local/bin/python | It looks like bitbake doesn't know how to build python. What is your bblayers.conf like ? python 2.7 is in poky/meta, is it included in your config? Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] question about SmartPM install from local file
Hi, I'm trying to get a better hand on how smart work. I've been successful to create a repo, update and install from it. Now I want to go further. Let's assume: - I have a working repo and a working device - I build a new recipe (here, git) and update my repo - I "smart update" on my device Now instead of installing, I choose to "download" the package : # smart download git It's successful. Now I want to install it : # smart install ./git-1.8.1.4-r0.armv6_vfp.rpm Loading cache... error: Unable to create channel for file: ./git-1.8.1.4-r0.armv6_vfp.rpm Whatever I do I end up with this error. Does it ring a bell to anyone? Is this the right place to ask? Thanks a lot for your help Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Issue with SmartPM install from file
Hi, I'm trying to get a better hand on how smart work. I've been successful to create a repo, update and install from it. Now I want to go further. Let's assume: - I have a working repo and a working device - I build a new recipe (here, git) and update my repo - I "smart update" on my device Now instead of installing, I choose to "download" the package : # smart download git It's successful. Now I want to install it : # smart install ./git-1.8.1.4-r0.armv6_vfp.rpm Loading cache... error: Unable to create channel for file: ./git-1.8.1.4-r0.armv6_vfp.rpm Whatever I do I end up with this error. Does it ring a bell to anyone? Is this the right place to ask? Thanks a lot for your help Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] phusion passenger
Hi, Has anyone tried and succeeded to build passenger for apache2 within Yocto ? I've tried to do this inside a Yocto distro booting on Raspberry and have a strange failure as shown below. I checked and of course I have string.h in /usr/include... More importantly, has anyone any guideline about how to _cross-compile_ passenger ? I don't want to build it directly on the device, I want to build it from my PC and deploy it in my distrib. Thanks for any possible help ! Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] misleading dependencies between packages
Hi, I have many issues with Apache2 package so I thought I would reinstall it. I used smart (smart install apache2) and here is the very strange issue I got: Installing packages (20): apache2-2.4.3-r1@armv6_vfp libgdbm4-1.10-r3@armv6_vfp busybox-1.20.2-r8@armv6_vfp libpcre1-8.32-r1@armv6_vfp busybox-syslog-1.20.2-r8@armv6_vfp libperl5-5.14.3-r1@armv6_vfp busybox-udhcpc-1.20.2-r8@armv6_vfp libssl1.0.0-1.0.1e-r15.0@armv6_vfp libapr-1-0-1.4.6-r2@armv6_vfp libuuid1-2.22.2-r3@armv6_vfp libaprutil-1-0-1.5.1-r0@armv6_vfp libz1-1.2.7-r0@armv6_vfp libc6-2.17-r3@armv6_vfp openssl-1.0.1e-r15.0@armv6_vfp libcrypto1.0.0-1.0.1e-r15.0@armv6_vfp perl-5.14.3-r1@armv6_vfp libexpat1-2.1.0-r0@armv6_vfp update-alternatives-cworth-1:0.1.8+svnr649-r13.0@armv6_vfp libgcc1-4.7.2-r20@armv6_vfp update-rc.d-0.7-r5@all 4.8MB of package files are needed. 9.7MB will be used. Confirm changes? (Y/n): Y Fetching packages... [Snip lots of downloads] -> http://192.168.0.50:81/rpm/armv6_vfp/apache2-2.4.3-r1.armv6_vfp.rpm apache2-2.4.3-r1.armv6_vfp.rpm ## [ 95%] error: Failed to download packages: error: http://192.168.0.50:81/rpm/armv6_vfp/libuuid1-2.22.2-r3.armv6_vfp.rpm: File not found And indeed, I do not have r3 of libuuid1 but r5. This is not the first time I run in this issue, it's unfortunately quite common. And I can't even figure who is generating libuuid1 :( Any idea? Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] error in : $ runqemu qemux86
On lun., sept. 9, 2013 at 10:01 PM, Arun M Kumar mailto:arunkr.li...@gmail.com";>> wrote: I have built my first image with the Yocto Project build environment, I have the image ready. when I do. $ runqemu qemux86 I get the following error. There was an error running bitbake to determine TMPDIR Here is the output from 'bitbake -e': ERROR: Unable to parse conf/bitbake.conf: conf/bitbake.conf:18: unparsed line: 'xport exec_prefix = "/usr"' _ What could be the possible causes to this. How did you generate your image? Did you run the oe-.. Script first ? Jay I had to add the scripts directory in Poky to my PATH variable, does this gives any hints to my problem ? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: misleading dependencies between packages
Hi JCP
Thanks for your information, here are the next questions:
libuuid is provided by util-linux. Check in meta/recipes-core/util-linux
for more details.
r3 is PR that util-linux has in dylan 9.0.1. Unless you change the PR,
it will be r3 only. I am not sure how you end up with r5.
May be you need to (re)build util-linux if you need libuuid. Also You
should check with the dependencies,
I see apr package which depends on util-linux.
Just to make sure, I did :
bitbake util-linux -c cleanall
bitbake util-linux
It will try to fetch:
0: util-linux-2.22.2-r5 do_fetch (pid 2420)
Which explains why I end up with a -r5 package
Looking at util-linux.inc, I see it tries to download the
SRC_URI =
"${KERNELORG_MIRROR}/linux/utils/util-linux/v${MAJOR_VERSION}/util-linux-${PV}.tar.bz2
\
So ${PV} is set somewhere else to r5, but not in this package. I don't
know why/how it is fixed to something else. Could it be an issue like PV
is set by another package, and not reset? Otherwise I can't figure how
it comes out as "r5".
In the bb file I have ${PR} set to "r3". May be it should be what
SRC_URI uses?
Jay
Hope this helps.
Cheers,
On Tue, Sep 10, 2013 at 12:08 PM, JC <mailto:j...@vtkloud.com>> wrote:
Hi,
I have many issues with Apache2 package so I thought I would
reinstall it. I used smart (smart install apache2) and here is the
very strange issue I got:
Installing packages (20):
apache2-2.4.3-r1@armv6_vfp libgdbm4-1.10-r3@armv6_vfp
busybox-1.20.2-r8@armv6_vfp libpcre1-8.32-r1@armv6_vfp
busybox-syslog-1.20.2-r8@armv6_vfp libperl5-5.14.3-r1@armv6_vfp
busybox-udhcpc-1.20.2-r8@armv6_vfp libssl1.0.0-1.0.1e-r15.0@armv6_vfp
libapr-1-0-1.4.6-r2@armv6_vfp libuuid1-2.22.2-r3@armv6_vfp
libaprutil-1-0-1.5.1-r0@armv6_vfp libz1-1.2.7-r0@armv6_vfp
libc6-2.17-r3@armv6_vfp openssl-1.0.1e-r15.0@armv6_vfp
libcrypto1.0.0-1.0.1e-r15.0@armv6_vfp perl-5.14.3-r1@armv6_vfp
libexpat1-2.1.0-r0@armv6_vfp
update-alternatives-cworth-1:0.1.8+svnr649-r13.0@armv6_vfp
libgcc1-4.7.2-r20@armv6_vfp update-rc.d-0.7-r5@all
4.8MB of package files are needed. 9.7MB will be used.
Confirm changes? (Y/n): Y
Fetching packages...
[Snip lots of downloads]
-> http://192.168.0.50:81/rpm/armv6_vfp/apache2-2.4.3-r1.armv6_vfp.rpm
apache2-2.4.3-r1.armv6_vfp.rpm
##
[ 95%]
error: Failed to download packages:
error:
http://192.168.0.50:81/rpm/armv6_vfp/libuuid1-2.22.2-r3.armv6_vfp.rpm:
File not found
And indeed, I do not have r3 of libuuid1 but r5. This is not the
first time I run in this issue, it's unfortunately quite common.
And I can't even figure who is generating libuuid1 :(
Any idea?
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
--
JCP
--
JCP
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] misleading dependencies between packages
Dear Yi, 1. If your remote repo has updated, you need to recreate the repodata by using createrepo 2. You need to run "smart update" to update the information before run "smart install package". If you want to install package from remote repo, "smart update" is required because "smart install package" doesn't update the information automatically. Yep. I did both of course. But even without it: an update would go from r3 to r5, probably not the reverse :( But yes, I ran both commands prior to this failure Best regards, Jay Thanks, Yi And indeed, I do not have r3 of libuuid1 but r5. This is not the first time I run in this issue, it's unfortunately quite common. And I can't even figure who is generating libuuid1 :( Any idea? Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with SmartPM install from file
On 10/09/2013 09:28, Yi Zhao wrote: 于 2013年09月10日 03:33, JC 写道: Hi, I'm trying to get a better hand on how smart work. I've been successful to create a repo, update and install from it. Now I want to go further. Let's assume: - I have a working repo and a working device - I build a new recipe (here, git) and update my repo - I "smart update" on my device Now instead of installing, I choose to "download" the package : # smart download git It's successful. Now I want to install it : # smart install ./git-1.8.1.4-r0.armv6_vfp.rpm Loading cache... error: Unable to create channel for file: ./git-1.8.1.4-r0.armv6_vfp.rpm That because there is no rpm-sys channel in your target. You could run "smart channel --show" to check it. # smart channel --show [rpmsys] type = rpm-sys The rpm-sys channel is a default channel. It should be created when build the rootfs. It is present :( Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] curl smart package requires curl-cert... another strange smart dependency issue
Did anyone already had this very strange issue installing curl ? Computing transaction... error: Can't install libcurl5-7.29.0-r1@armv6_vfp: no package provides curl-certs I have more and more issues with smart... Is there any specific discussion channel for it? Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] broken meta-baryon?
Hi I was trying to give a look at Baryon, but I can't bake it. It seems there's a package whose sources have vanised : ERROR: Fetcher failure for URL: 'http://code.entropywave.com/download/orc/orc-0.4.5.tar.gz;name=orc'. Checksum mismatch! File: '/media/yocto/downloads/orc-0.4.5.tar.gz' has md5 checksum 5b6d74f1453e20c09d6a20d909779ad7 when e26e59428b13ec251916f34bea96eee5 was expected File: '/media/yocto/downloads/orc-0.4.5.tar.gz' has sha256 checksum 6f0e2620a2a986c8329612f1db92f273949a58480290ace72eca7f1dba1a5c98 when 4e04953643cd8e67f8d9796da9547a606954e3944e42e7ce5a099440fd8e729e was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[orc.md5sum] = "5b6d74f1453e20c09d6a20d909779ad7" SRC_URI[orc.sha256sum] = "6f0e2620a2a986c8329612f1db92f273949a58480290ace72eca7f1dba1a5c98" Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. Is the Baryon maintainer aware of this or is this just me ? Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Trying to install some cpan modules - dumper.so wrong ELF class???
Hi,
I need a few CPAN modules. For most of them I had no issue with a common
recipe, but I end up with issues on Net::SDP
here's my recipe :
SUMMARY = "Collection of Perl modules for working with shairport."
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
SRC_URI = "http://www.cpan.org/modules/by-module/Net/${BPN}-${PV}.tar.gz "
SRC_URI[md5sum] = "bb70cb8ebb7ca57c20ac134ac4499e66"
SRC_URI[sha256sum] =
"f43fa0f8f9705ae66a4084d13691c2ad7724b381424d368404c3d825bc5782f0"
require cpan.inc
and cpan.inc is :
S= "${WORKDIR}/${BPN}-${PV}"
inherit cpan
do_compile() {
export LIBC="$(find ${STAGING_DIR_TARGET}/${base_libdir}/ -name
'libc-*.so')"
cpan_do_compile
}
Here's the error message:
Can't load
'/media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so'
for module Data::Dumper:
/media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so:
wrong ELF class: ELFCLASS32 at
/media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.14.3/XSLoader.pm
li
Does it ring a bell to anyone ???
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] broken meta-baryon?
On Monday, September 16, 2013, Paul Eggleton wrote: > Hi Jay, > > > > > > Is the Baryon maintainer aware of this or is this just me ? > > Looks like the upstream website for orc has completely broken, > unfortunately, > and unlike the core recipes the source is not on our source mirror. I've > sent > an email to get it mirrored on sources.openembedded.org until upstream > wakes > up (assuming it does). > > Thanks Paul, let's see what happens :) Jay > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trying to install some cpan modules - dumper.so wrong ELF class???
On 25/09/2013 21:40, Khem Raj wrote: On Wed, Sep 25, 2013 at 12:32 PM, Jean-Charles JC Verdié wrote: Can't load '/media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so' for module Data::Dumper: /media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so: wrong ELF class: ELFCLASS32 at /media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.14.3/XSLoader.pm li this is reaching out to native-perl mods there. seems its not cross compiler friendly look out for variables that are being used to construct path for XSLoader.pm and use the correct target paths Actually, it seems that this package does not provide the regular .PL file expected by cpan. I found out a way to generate it, and I could compile. But as you can see it uses perl native (I get an x86-64 build), and it's trying to install on my / directory instead of the rootfs: ERROR: Logfile of failure stored in: /media/yocto/yocto/rpi/tmp/work/armv6-vfp-poky-linux-gnueabi/Net-SDP/0.07-r0/temp/log.do_install.30179 Log data follows: | DEBUG: Executing shell function do_install | Building Net-SDP | WARNING: Can't figure out install path for types: bindoc libdoc | Files will not be installed. | | ERROR: Can't create '/usr/lib/perl/site_perl/5.14.3/Net' | mkdir /usr/lib/perl/site_perl: Permission denied at /media/yocto/yocto/rpi/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl//5.14.3/ExtUtils/Install.pm line 494 | | | at /media/yocto/yocto/rpi/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.14.3/Module/Build/Base.pm line 3569 FWIW, I can do the manual operations in qemu so it's really a matter of using target perl instead of hosted perl I think :( I'm investigating a little bit more or I will post additional information for help :) Thanks anyway, Regards Jay ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ${libdir} usage
Hi,
I'm currently putting together a bunch of recipes to install some cpan
modules. I had some complaints by bitbake about files being installed
but not shipped.
I figured that I need to populate FILES_{PN} but I'm not clear about
what I should do with it: use ${libdir}, use "usr/*" ? Knowing that my
image(s) directories mostly contain usr/lib/perl/* and sometimes usr/bin/*
What's the best practice ? That'll save me some time when I send the
patch :)
Thanks for your help
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Trying to install some cpan modules - dumper.so wrong ELF class???
Hi Yoctoers,
Anyone got any idea about this previous mail ?
On 14Sep 2013, at 5:36 PM, JC wrote:
> I need a few CPAN modules. For most of them I had no issue with a common
> recipe, but I end up with issues on Net::SDP
>
> here's my recipe :
> SUMMARY = "Collection of Perl modules for working with shairport."
> SECTION = "libs"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>
> SRC_URI = "http://www.cpan.org/modules/by-module/Net/${BPN}-${PV}.tar.gz "
>
> SRC_URI[md5sum] = "bb70cb8ebb7ca57c20ac134ac4499e66"
> SRC_URI[sha256sum] =
> "f43fa0f8f9705ae66a4084d13691c2ad7724b381424d368404c3d825bc5782f0"
>
> require cpan.inc
>
> and cpan.inc is :
> S= "${WORKDIR}/${BPN}-${PV}"
>
> inherit cpan
>
> do_compile() {
>export LIBC="$(find ${STAGING_DIR_TARGET}/${base_libdir}/ -name
> 'libc-*.so')"
>cpan_do_compile
> }
>
>
> Here's the error message:
>
> Can't load
> '/media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so'
> for module Data::Dumper:
> /media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/qemuarm/usr/lib/perl/5.14.3/auto/Data/Dumper/Dumper.so:
> wrong ELF class: ELFCLASS32 at
> /media/yocto/var_yocto/var_yocto/rpi-build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.14.3/XSLoader.pm
> li
>
>
> Does it ring a bell to anyone ???
>
I'd be willing to fix it, but I simply have no clue where to start :(
Regards
Jay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ${libdir} usage
On 10Oct 2013, at 12:01 PM, Paul Eggleton wrote:
> Hi Jay,
>
> On Wednesday 02 October 2013 00:02:11 JC wrote:
>> I'm currently putting together a bunch of recipes to install some cpan
>> modules. I had some complaints by bitbake about files being installed
>> but not shipped.
>>
>> I figured that I need to populate FILES_{PN} but I'm not clear about
>> what I should do with it: use ${libdir}, use "usr/*" ? Knowing that my
>> image(s) directories mostly contain usr/lib/perl/* and sometimes usr/bin/*
>
> Ultimately it depends on how those files have ended up there. If files have
> been
> installed in in /usr/lib because they've been installed in ${libdir} (this is
> the default for all autotooled recipes), then you should also use ${libdir}
> to
> match in FILES in case that value changes - some distros do this to flatten
> out
> /usr altogether for example.
>
Thanks !
Actually, I made a mistake and need to install those pm files in /lib not
/usr/lib. cpan (instead of cpan-build) did everything ok :)
Regards
Jay
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
