[yocto] question about toaster in yocto 1.7
Hi all I have read the Toaster Manual 1.7 and have a question : The toaster still can't launch a build in yocto 1.7 ? Thanks, Lei Maohui -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] do_install() is not getting called
Thanks Christian. It worked. I gave bitbake -c install to install it.
Regards
Hari
On Saturday, 8 November 2014 6:00 PM, Christian Ege k423...@gmail.com wrote:
Am 08.11.2014 13:10 schrieb hari kumar harikumar...@yahoo.co.in:
Hi All,
I am creating a new recipe in bsp layer. So I created a bb file inside the
recipe.
Then from the build directory, I am able to successfully compile the source
files and was able to create the library ( bitbake -c compile -f
package_name ). This is a makefile based package and I don't have an
install target in my Makefile. So I am writing a do_install in my bb file and
I am doing install there. I can see that do_compile task is getting called.
But do_install ( which was overridden in my bb file ) task is not called and
the images and libraries are not installed in the sysroots directory.
By running bitbake -f -c compile the do_install is not called. Either you call
bitbacke package_name or to force install butbake -c install.
Sometime a clean or cleanall before a compile also helps. This is needed if you
already had a successfull run.
Regards
Christian
Bitbake Snippet :
SRC_URI = file://src/
PV = 1.0
S = ${WORKDIR}/src/
EXTRA_OEMAKE = CFLAGS=--sysroot=${PKG_CONFIG_SYSROOT_DIR} 'LDFLAGS=-lpthread
-lrt ${LDFLAGS}'
do_install () {
oe_runmake install DESTDIR=${D} SBINDIR=${sbindir} MANDIR=${mandir}
INCLUDEDIR=${includedir}
install -d ${D}${includedir}/
for f in ${S}/*.h; do
install -m 0644 $f ${D}${includedir}/
done
}
PARALLEL_MAKE =
#BBCLASSEXTEND = native
Could you please suggest why do_install is not getting called for this
Makefile based system ?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
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] question about toaster in yocto 1.7
On 10/11/2014 10:23, Lei, Maohui leimao...@cn.fujitsu.com wrote: Hi all I have read the Toaster Manual 1.7 and have a question : The toaster still can't launch a build in yocto 1.7 ? Hi Lei, No, I am afraid Toaster still cannot launch builds in Yocto Project 1.7. We are working on it though, so Toaster should be able to launch builds in Yocto Project 1.8. If you want to help us make it happen (contributions sorely needed), let me know. Cheers Belén Thanks, Lei Maohui -- ___ 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] Unable to find the ncurses libraries when running menuconfig
Nick,
Yes this is a issue with your custom machine and I believe this is a issue with
your your machine
conf is located in the build directories.
Cheers Nick
On 14-11-10 02:26 AM, Nick D'Ademo wrote:
menuconfig works with a core-image-minimal vanilla build:
*Build Configuration:BB_VERSION= 1.24.0BUILD_SYS =
x86_64-linuxNATIVELSBSTRING = Ubuntu-14.04TARGET_SYS=
arm-poky-linux-gnueabiMACHINE = qemuarmDISTRO=
pokyDISTRO_VERSION= 1.7TUNE_FEATURES = arm armv5 thumb
dspTARGET_FPU= softmeta meta-yocto
meta-yocto-bsp=
master:45bb9e3323073070453647a32289dc1792f3d660meta-oe
meta-multimedia meta-gnome=
master:dac2422f737c351c37a8405a76b5f0b5df9311a0*
So this must be an issue with my custom machine.
On Mon, Nov 10, 2014 at 2:43 PM, nick xerofo...@gmail.com wrote:
Nick,
Then this is an issue with your machine conf or paths required for kernel
building. Are you able
to build a poky distro with a working kernel and this is just a issue with
you building the yocto
kernel alone or can you also not build poky too?
Cheers Nick
On 14-11-09 10:36 PM, Nick D'Ademo wrote:
Just tried with the latest 3.17.2 kernel. 'make menuconfig' works fine
and
loads the interactive kernel config.
On Mon, Nov 10, 2014 at 2:01 PM, nick xerofo...@gmail.com wrote:
Try downloading a stock kernel for kernel.org and extract it in your
home
directory and run make menuconfig in
the root of the kernel source tree, if this works then I am assuming
either ncurses or your machine conf is wrong
somewhere.
Cheers Nick
On 14-11-09 09:51 PM, Nick D'Ademo wrote:
Hi Nick,
I removed build/tmp/ and performed a rebuild - I'm still experiencing
the
same error message unfortunately.
On Mon, Nov 10, 2014 at 12:58 PM, nick xerofo...@gmail.com wrote:
Seems to after reading and doing some research a build issue with
multiple
jobs or try running rm -r tmp in your
build and then rebuild as it may be an issue with out of date temp
files.
Cheers Nick
On 14-11-09 08:51 PM, Nick D'Ademo wrote:
Thanks for trying that out Nick.
Issue is present on both 3.14 and 3.17 for me.
All paths in the require lines are correct too.
Any other ideas?
On Mon, Nov 10, 2014 at 12:46 PM, nick xerofo...@gmail.com wrote:
I tried bitbake linux-yocto -c menuconfig on my own system running
the
same distro and it seems to my
default use kernel 3.14 not 3.17 otherwise this seems be fine from
my
understanding. Also check all the
paths in your require lines as there may be an issue with your
builds
and
the path set up by these files
that you are linking to for your kernel build.
Nick
On 14-11-09 08:40 PM, Nick D'Ademo wrote:
Thanks Nick.
Machine conf is as follows (it's actually nearly identical to
nuc.conf
-
however, BT support, multilib, and preferred providers have been
added):
#@TYPE: Machine
#@NAME: chiefriver
#@WEBTITLE: Intel Next Unit of Computing (NUC) Model: DC3217IYE
#@DESCRIPTION: Machine configuration for Intel NUC model DC3217IYE
# i.e. Ivy Bridge + Panther Point
PREFERRED_VERSION_linux-yocto ?= 3.17%
MACHINE_FEATURES += va-impl-intel wifi efi bluetooth
MACHINE_FEATURES += intel-ucode
require conf/machine/include/meta-intel.inc
require conf/machine/include/intel-corei7-64-common.inc
require conf/machine/include/intel-common-pkgarch.inc
require multilib.conf
MACHINE_HWCODECS ?= va-intel gst-va-intel
XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
${XSERVER_X86_I965} \
MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2b-6
lms8
# disable the serial port configuration
SERIAL_CONSOLE =
PREFERRED_PROVIDER_jpeg = jpeg
PREFERRED_PROVIDER_jpeg-native = jpeg-native
PREFERRED_PROVIDER_virtual/fftw = fftw
On Mon, Nov 10, 2014 at 12:36 PM, nick xerofo...@gmail.com
wrote:
Hey Nick,
This seems to then be an issue with incorrect paths or build
information
in your nuc.conf
as the most likely culprit. If you can post your machine's conf
file I
will be glad to see
if there are any issues I can spot.
Nick
On 14-11-09 08:33 PM, Nick D'Ademo wrote:
1) source oe-init-build-env is run before building.
2) We are actually using a custom machine .conf based on
nuc.conf,
so
actually: MACHINE = custom_machine_name. I replaced it with
nuc
in
this
post to avoid confusion.
On Mon, Nov 10, 2014 at 12:25 PM, nick xerofo...@gmail.com
wrote:
Do you run source oe-init-build-env before building and why is
your
machine
set to nuc seems this may be an issue?
Nick
On 14-11-09 08:15 PM, Nick D'Ademo wrote:
Thanks for the quick reply Nick.
Host system is Ubuntu 14.04. ncurses is already installed:
sudo apt-get install libncurses5-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libncurses5-dev is already the newest version.
On Mon, Nov 10,
Re: [yocto] Unable to find the ncurses libraries when running menuconfig
If I do the following (from the same Terminal that *oe-init-build-env *has
been run):
1) cd
/home/nick/poky/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.17.1+gitAUTOINC+b86dd5c6f4_0caf16d385-r0/linux-corei7-64-intel-common-standard-build
2) make menuconfig
Menu config loads correctly.
So for some reason, 'bitbake linux-yocto -c menuconfig' is not invoking
menuconfig properly.
Any ideas where to look in regard to my custom machine config?
On Mon, Nov 10, 2014 at 10:11 PM, nick xerofo...@gmail.com wrote:
Nick,
Yes this is a issue with your custom machine and I believe this is a issue
with your your machine
conf is located in the build directories.
Cheers Nick
On 14-11-10 02:26 AM, Nick D'Ademo wrote:
menuconfig works with a core-image-minimal vanilla build:
*Build Configuration:BB_VERSION= 1.24.0BUILD_SYS =
x86_64-linuxNATIVELSBSTRING = Ubuntu-14.04TARGET_SYS=
arm-poky-linux-gnueabiMACHINE = qemuarmDISTRO=
pokyDISTRO_VERSION= 1.7TUNE_FEATURES = arm armv5 thumb
dspTARGET_FPU= softmeta meta-yocto
meta-yocto-bsp=
master:45bb9e3323073070453647a32289dc1792f3d660meta-oe
meta-multimedia meta-gnome=
master:dac2422f737c351c37a8405a76b5f0b5df9311a0*
So this must be an issue with my custom machine.
On Mon, Nov 10, 2014 at 2:43 PM, nick xerofo...@gmail.com wrote:
Nick,
Then this is an issue with your machine conf or paths required for
kernel
building. Are you able
to build a poky distro with a working kernel and this is just a issue
with
you building the yocto
kernel alone or can you also not build poky too?
Cheers Nick
On 14-11-09 10:36 PM, Nick D'Ademo wrote:
Just tried with the latest 3.17.2 kernel. 'make menuconfig' works fine
and
loads the interactive kernel config.
On Mon, Nov 10, 2014 at 2:01 PM, nick xerofo...@gmail.com wrote:
Try downloading a stock kernel for kernel.org and extract it in your
home
directory and run make menuconfig in
the root of the kernel source tree, if this works then I am assuming
either ncurses or your machine conf is wrong
somewhere.
Cheers Nick
On 14-11-09 09:51 PM, Nick D'Ademo wrote:
Hi Nick,
I removed build/tmp/ and performed a rebuild - I'm still experiencing
the
same error message unfortunately.
On Mon, Nov 10, 2014 at 12:58 PM, nick xerofo...@gmail.com wrote:
Seems to after reading and doing some research a build issue with
multiple
jobs or try running rm -r tmp in your
build and then rebuild as it may be an issue with out of date temp
files.
Cheers Nick
On 14-11-09 08:51 PM, Nick D'Ademo wrote:
Thanks for trying that out Nick.
Issue is present on both 3.14 and 3.17 for me.
All paths in the require lines are correct too.
Any other ideas?
On Mon, Nov 10, 2014 at 12:46 PM, nick xerofo...@gmail.com
wrote:
I tried bitbake linux-yocto -c menuconfig on my own system running
the
same distro and it seems to my
default use kernel 3.14 not 3.17 otherwise this seems be fine from
my
understanding. Also check all the
paths in your require lines as there may be an issue with your
builds
and
the path set up by these files
that you are linking to for your kernel build.
Nick
On 14-11-09 08:40 PM, Nick D'Ademo wrote:
Thanks Nick.
Machine conf is as follows (it's actually nearly identical to
nuc.conf
-
however, BT support, multilib, and preferred providers have been
added):
#@TYPE: Machine
#@NAME: chiefriver
#@WEBTITLE: Intel Next Unit of Computing (NUC) Model: DC3217IYE
#@DESCRIPTION: Machine configuration for Intel NUC model
DC3217IYE
# i.e. Ivy Bridge + Panther Point
PREFERRED_VERSION_linux-yocto ?= 3.17%
MACHINE_FEATURES += va-impl-intel wifi efi bluetooth
MACHINE_FEATURES += intel-ucode
require conf/machine/include/meta-intel.inc
require conf/machine/include/intel-corei7-64-common.inc
require conf/machine/include/intel-common-pkgarch.inc
require multilib.conf
MACHINE_HWCODECS ?= va-intel gst-va-intel
XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
${XSERVER_X86_I965} \
MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2b-6
lms8
# disable the serial port configuration
SERIAL_CONSOLE =
PREFERRED_PROVIDER_jpeg = jpeg
PREFERRED_PROVIDER_jpeg-native = jpeg-native
PREFERRED_PROVIDER_virtual/fftw = fftw
On Mon, Nov 10, 2014 at 12:36 PM, nick xerofo...@gmail.com
wrote:
Hey Nick,
This seems to then be an issue with incorrect paths or build
information
in your nuc.conf
as the most likely culprit. If you can post your machine's conf
file I
will be glad to see
if there are any issues I can spot.
Nick
On 14-11-09 08:33 PM, Nick D'Ademo wrote:
1) source oe-init-build-env is run before building.
2) We are actually using a
Re: [yocto] newbb.vim vs skeleton recipe in yocto-docs dev manual....
newbb.vim needs to be patched.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Bob Cochran
Sent: Sunday, November 09, 2014 1:14 PM
To: Yocto discussion list
Subject: [yocto] newbb.vim vs skeleton recipe in yocto-docs dev manual
Hi,
I just noticed that newbb.vim in bitbake/contrib is notably different from the
skeleton recipe proposed in the latest Dev Manual.
I'll submit a patch if someone can give me some guidance on what should be
in newbb.vim (or maybe it's the manual that needs to be patched).
Bob
From yocto-docs: Dev Manual (modify the following skeleton recipe):
SUMMARY =
HOMEPAGE =
LICENSE =
LIC_FILES_CHKSUM =
SRC_URI =
SRC_URI[md5sum] =
SRC_URI[sha256sum] =
S = ${WORKDIR}/${PN}-${PV}
From newbb.vim:
DESCRIPTION =
HOMEPAGE =
LICENSE =
SECTION =
DEPENDS =
SRC_URI =
--
___
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] newbb.vim vs skeleton recipe in yocto-docs dev manual....
On 11/10/2014 09:28 AM, Rifenbark, Scott M wrote:
newbb.vim needs to be patched.
Thanks Scott. I'll submit a patch later this week. Let me see if
anyone else wants to provide input on what should be in the template.
Bob
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Bob Cochran
Sent: Sunday, November 09, 2014 1:14 PM
To: Yocto discussion list
Subject: [yocto] newbb.vim vs skeleton recipe in yocto-docs dev manual
Hi,
I just noticed that newbb.vim in bitbake/contrib is notably different from the
skeleton recipe proposed in the latest Dev Manual.
I'll submit a patch if someone can give me some guidance on what should be
in newbb.vim (or maybe it's the manual that needs to be patched).
Bob
From yocto-docs: Dev Manual (modify the following skeleton recipe):
SUMMARY =
HOMEPAGE =
LICENSE =
LIC_FILES_CHKSUM =
SRC_URI =
SRC_URI[md5sum] =
SRC_URI[sha256sum] =
S = ${WORKDIR}/${PN}-${PV}
From newbb.vim:
DESCRIPTION =
HOMEPAGE =
LICENSE =
SECTION =
DEPENDS =
SRC_URI =
--
___
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] Unable to find the ncurses libraries when running menuconfig
On Mon, Nov 10, 2014 at 7:56 AM, Nick D'Ademo nickdad...@gmail.com wrote:
If I do the following (from the same Terminal that oe-init-build-env has
been run):
1) cd
/home/nick/poky/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.17.1+gitAUTOINC+b86dd5c6f4_0caf16d385-r0/linux-corei7-64-intel-common-standard-build
2) make menuconfig
Menu config loads correctly.
So for some reason, 'bitbake linux-yocto -c menuconfig' is not invoking
menuconfig properly.
Any ideas where to look in regard to my custom machine config?
On Mon, Nov 10, 2014 at 10:11 PM, nick xerofo...@gmail.com wrote:
Nick,
Yes this is a issue with your custom machine and I believe this is a issue
with your your machine
conf is located in the build directories.
Cheers Nick
On 14-11-10 02:26 AM, Nick D'Ademo wrote:
menuconfig works with a core-image-minimal vanilla build:
*Build Configuration:BB_VERSION= 1.24.0BUILD_SYS =
x86_64-linuxNATIVELSBSTRING = Ubuntu-14.04TARGET_SYS=
arm-poky-linux-gnueabiMACHINE = qemuarmDISTRO=
pokyDISTRO_VERSION= 1.7TUNE_FEATURES = arm armv5 thumb
dspTARGET_FPU= softmeta meta-yocto
meta-yocto-bsp=
master:45bb9e3323073070453647a32289dc1792f3d660meta-oe
meta-multimedia meta-gnome=
master:dac2422f737c351c37a8405a76b5f0b5df9311a0*
So this must be an issue with my custom machine.
On Mon, Nov 10, 2014 at 2:43 PM, nick xerofo...@gmail.com wrote:
Nick,
Then this is an issue with your machine conf or paths required for
kernel
building. Are you able
to build a poky distro with a working kernel and this is just a issue
with
you building the yocto
kernel alone or can you also not build poky too?
Cheers Nick
On 14-11-09 10:36 PM, Nick D'Ademo wrote:
Just tried with the latest 3.17.2 kernel. 'make menuconfig' works fine
and
loads the interactive kernel config.
On Mon, Nov 10, 2014 at 2:01 PM, nick xerofo...@gmail.com wrote:
Try downloading a stock kernel for kernel.org and extract it in your
home
directory and run make menuconfig in
the root of the kernel source tree, if this works then I am assuming
either ncurses or your machine conf is wrong
somewhere.
Cheers Nick
On 14-11-09 09:51 PM, Nick D'Ademo wrote:
Hi Nick,
I removed build/tmp/ and performed a rebuild - I'm still
experiencing
the
same error message unfortunately.
On Mon, Nov 10, 2014 at 12:58 PM, nick xerofo...@gmail.com wrote:
Seems to after reading and doing some research a build issue with
multiple
jobs or try running rm -r tmp in your
build and then rebuild as it may be an issue with out of date temp
files.
Cheers Nick
On 14-11-09 08:51 PM, Nick D'Ademo wrote:
Thanks for trying that out Nick.
Issue is present on both 3.14 and 3.17 for me.
All paths in the require lines are correct too.
Any other ideas?
On Mon, Nov 10, 2014 at 12:46 PM, nick xerofo...@gmail.com
wrote:
I tried bitbake linux-yocto -c menuconfig on my own system
running
the
same distro and it seems to my
default use kernel 3.14 not 3.17 otherwise this seems be fine
from
my
understanding. Also check all the
paths in your require lines as there may be an issue with your
builds
and
the path set up by these files
that you are linking to for your kernel build.
Nick
On 14-11-09 08:40 PM, Nick D'Ademo wrote:
Thanks Nick.
Machine conf is as follows (it's actually nearly identical to
nuc.conf
-
however, BT support, multilib, and preferred providers have been
added):
#@TYPE: Machine
#@NAME: chiefriver
#@WEBTITLE: Intel Next Unit of Computing (NUC) Model: DC3217IYE
#@DESCRIPTION: Machine configuration for Intel NUC model
DC3217IYE
# i.e. Ivy Bridge + Panther Point
PREFERRED_VERSION_linux-yocto ?= 3.17%
MACHINE_FEATURES += va-impl-intel wifi efi bluetooth
MACHINE_FEATURES += intel-ucode
require conf/machine/include/meta-intel.inc
require conf/machine/include/intel-corei7-64-common.inc
require conf/machine/include/intel-common-pkgarch.inc
require multilib.conf
MACHINE_HWCODECS ?= va-intel gst-va-intel
XSERVER ?= ${XSERVER_X86_BASE} \
${XSERVER_X86_EXT} \
${XSERVER_X86_I965} \
MACHINE_EXTRA_RRECOMMENDS += linux-firmware-iwlwifi-6000g2b-6
lms8
# disable the serial port configuration
SERIAL_CONSOLE =
PREFERRED_PROVIDER_jpeg = jpeg
PREFERRED_PROVIDER_jpeg-native = jpeg-native
PREFERRED_PROVIDER_virtual/fftw = fftw
On Mon, Nov 10, 2014 at 12:36 PM, nick xerofo...@gmail.com
wrote:
Hey Nick,
This seems to then be an issue with incorrect paths or build
information
in your nuc.conf
as the most likely culprit. If you can post your machine's conf
file I
will be glad to see
if there are any issues I can spot.
Nick
On 14-11-09 08:33 PM, Nick D'Ademo
[yocto] Truncated 64 bit return from kernel space
Hello all, I have a custom kernel module driver that returns a truncated 64-bit value. The first 32-bits are missing. The driver is called using llseek() and the address used in user space and in kernel space is 64-bits, but when returning from kernel space, the first 32-bits gets truncated, only returning the second half. I've used printk on the address value before returning it in the driver and it is the full 64-bit address. The return is using loff_t, and I'm using a genericx86-64 Linux kernel. Any thoughts? Thanks, - Anthony B. Padua -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH] checkpolicy: remove link against libfl
An updated version of the patch to drop linking against libfl was
required.
Signed-off-by: Joe MacDonald joe_macdon...@mentor.com
---
recipes-security/selinux/checkpolicy.inc| 2 +-
.../selinux/checkpolicy/checkpolicy-Do-not-link-against-libfl.patch | 6 --
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/recipes-security/selinux/checkpolicy.inc
b/recipes-security/selinux/checkpolicy.inc
index 1a21680..e0c7377 100644
--- a/recipes-security/selinux/checkpolicy.inc
+++ b/recipes-security/selinux/checkpolicy.inc
@@ -11,7 +11,7 @@ LICENSE = GPLv2+
DEPENDS += libsepol libselinux bison-native flex-native
-#SRC_URI += file://checkpolicy-Do-not-link-against-libfl.patch
+SRC_URI += file://checkpolicy-Do-not-link-against-libfl.patch
EXTRA_OEMAKE += PREFIX=${D}
EXTRA_OEMAKE += LEX='flex'
diff --git
a/recipes-security/selinux/checkpolicy/checkpolicy-Do-not-link-against-libfl.patch
b/recipes-security/selinux/checkpolicy/checkpolicy-Do-not-link-against-libfl.patch
index 6fcf459..e19209e 100644
---
a/recipes-security/selinux/checkpolicy/checkpolicy-Do-not-link-against-libfl.patch
+++
b/recipes-security/selinux/checkpolicy/checkpolicy-Do-not-link-against-libfl.patch
@@ -8,6 +8,8 @@ no longer get errors about undefined references to yylex.
Upstream-status: Pending
Signed-off-by: Chong Lu chong...@windriver.com
+Signed-off-by: Shrikant Bobade shrikant_bob...@mentor.com¶
+
---
Makefile |2 +-
test/Makefile |2 +-
@@ -34,8 +36,8 @@ index 63b4d24..0f19a8a 100644
CFLAGS ?= -g -Wall -W -Werror -O2 -pipe
override CFLAGS += -I$(INCLUDEDIR)
--LDLIBS=-lfl -lselinux $(LIBDIR)/libsepol.a -L$(LIBDIR)
-+LDLIBS=-lselinux $(LIBDIR)/libsepol.a -L$(LIBDIR)
+-LDLIBS=-lfl $(LIBDIR)/libsepol.a -L$(LIBDIR)
++LDLIBS=$(LIBDIR)/libsepol.a -L$(LIBDIR)
all: dispol dismod
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Release Candidate Build for yocto-1.6.2.rc2 now available.
-e A release candidate build for yocto-1.6.2.rc2 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.2.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : d9eaf5edeb848671db0a7ac864850833af82bef2 meta-fsl-arm : 9bc540eec9a7e280af13371ea70650fcc47ea627 meta-minnow : 58fd55eb321a875d4e51c5c430de4d725ec9ba4c meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 299f84cceccacd84651c1cefc1c34e66fb598a96 poky : 30b8d9378b8260e452552b806610dc9b6fe0b69f This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Making Hob better.
Hello everyone, I am new to the embedded space, been working with embedded for a couple of months now as well as Linux itself. After much time spent with Hob I have to say it's a awesome tool to use. However I would like it to be better than it already is, I see the potential of this interface to help newbies like myself, weather it be hobbyist or industrial use. So below is what I have found through my fiddling around with Hob. -Some interface inconsistencies when your selecting layers, image type, distro type etc. -Image deployments (Only .hddimg and .iso can be deployed to physical media at the end (To my knowledge) of the build process. There's is a lot of FS types, but I would really like to have a steps on how to install these other FS types which documentation nor simply goggling it helps) -Branding. There are ways to go and edit files to specify how to rebrand and stuff but that requires a command line. I would like to have the simple screen where I can add branding (Boot screens, Logos, and distro names etc.). I could definitely if Hob does have a Web User interface where I can't access a command line to change parameters of the finished product. -Documentation is awesome, however from a person that has only a year and a half experience using Linux it's kinda hard reading it sometimes. (Not really anything bad on Yocto's part. I would just like to input something that newbies can be represented in this project) I really could see Hob become a open source version of openSUSE Studio (Which it's closed source) but for embedded devices. So that's just my hopes for Hob / Yocto could become... Lastly, I would really love to help with development as well. I haven't really gotten into programming that much but I have worked with the Fedora Server Special Interest Group doing QA for Alpha and Beta release. So if anyone can put me in the right direction I can certainly help YP out. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Making Hob better.
John, Hob is not meant to be like Suse Studios. Further more you are right about the interface sucking hard for certain things, I would recommend you start cleaning that up first and then afterwards move on to other areas of interest with YP. Cheers Nick On 14-11-10 06:58 PM, John Unland wrote: Hello everyone, I am new to the embedded space, been working with embedded for a couple of months now as well as Linux itself. After much time spent with Hob I have to say it's a awesome tool to use. However I would like it to be better than it already is, I see the potential of this interface to help newbies like myself, weather it be hobbyist or industrial use. So below is what I have found through my fiddling around with Hob. -Some interface inconsistencies when your selecting layers, image type, distro type etc. -Image deployments (Only .hddimg and .iso can be deployed to physical media at the end (To my knowledge) of the build process. There's is a lot of FS types, but I would really like to have a steps on how to install these other FS types which documentation nor simply goggling it helps) -Branding. There are ways to go and edit files to specify how to rebrand and stuff but that requires a command line. I would like to have the simple screen where I can add branding (Boot screens, Logos, and distro names etc.). I could definitely if Hob does have a Web User interface where I can't access a command line to change parameters of the finished product. -Documentation is awesome, however from a person that has only a year and a half experience using Linux it's kinda hard reading it sometimes. (Not really anything bad on Yocto's part. I would just like to input something that newbies can be represented in this project) I really could see Hob become a open source version of openSUSE Studio (Which it's closed source) but for embedded devices. So that's just my hopes for Hob / Yocto could become... Lastly, I would really love to help with development as well. I haven't really gotten into programming that much but I have worked with the Fedora Server Special Interest Group doing QA for Alpha and Beta release. So if anyone can put me in the right direction I can certainly help YP out. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
