Hi, I got build errors on Ubuntu 12.04 with this patch:
| DEBUG: Executing shell function do_configure
|
| ERROR: "gcc " cannot build an executable (is your linker broken?)
// Robert
On 06/21/2016 09:18 AM, Stephen Arnold wrote:
And I finally figured out git send-email no longer has a
The following changes since commit 7c1f1fc3d739d778886208d6833c34e6ca1dc148:
build-appliance-image: Add LC_ALL setting and drop pseudo pieces (2016-06-16
22:43:57 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/PU-20160623
http
Related patches are rebased.
util-linux-ng-2.16-mount_lock_path.patch is removed because there's
no _PATH_MOUNTED_LOCK in the latest codes.
util-linux-native.patch is removed because 2.28 version of util-linux
has taken mkostemp into consideration and provide fallback if mkostemp
fails.
Patches are rebased or removed for the latest version.
'python' is added to RDEPENDS of systemd-ptest.
systemd-bootchart is now seprated from systemd, thus removing the
related configuration items.
Signed-off-by: Chen Qi
---
meta/recipes-core/systemd/systemd.inc
0001-configure.ac-support-large-file-for-stat64.patch is removed as it's
a backported patch and is already in the latest codes.
Signed-off-by: Chen Qi
---
.../{dbus-test_1.10.6.bb => dbus-test_1.10.8.bb} | 4 +-
...onfigure.ac-support-large-file-for-stat64.patch | 53
Signed-off-by: Chen Qi
---
meta/recipes-support/bash-completion/bash-completion_2.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-support/bash-completion/bash-completion_2.1.bb
Signed-off-by: Chen Qi
---
.../systemd-bootchart/systemd-bootchart_230.bb | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
meta/recipes-devtools/systemd-bootchart/systemd-bootchart_230.bb
diff --git
Hi Robert,
On Tue, 2016-05-10 at 01:13 -0700, Robert Yang wrote:
> This is still WIP, I send this out to make sure that I won't walk on
> wrong way too far. Please feel free to give any comments.
>
> TODO:
> * Update the one which uses runqemu, such as oeqa
> * Boot EFI image
> * Boot multilib
From: Roy Li
Signed-off-by: Roy Li
---
...XATTR_NAME_CAPS-is-defined-when-it-is-use.patch | 32 ++
meta/recipes-support/libcap/libcap_2.25.bb | 5 ++--
2 files changed, 35 insertions(+), 2 deletions(-)
create
On 06/23/2016 04:17 PM, Richard Purdie wrote:
Hi Robert,
On Tue, 2016-05-10 at 01:13 -0700, Robert Yang wrote:
This is still WIP, I send this out to make sure that I won't walk on
wrong way too far. Please feel free to give any comments.
TODO:
* Update the one which uses runqemu, such as
On 22 June 2016 at 17:35, Burton, Ross wrote:
> The patch should explain why we're disabling the test application.
>
> If we don't build the test app then the "vte" package is pretty pointless:
>
> libvte:
> /usr/lib/libvte-2.91.so.0
>
On Mon, Jun 20, 2016 at 10:47:16AM -0700, Michael Halstead wrote:
> Hello,
>
> OpenEmbedded is nearly ready to upgrade to a new version of Patchwork.
> The new version offers several new features that will allow OpenEmbedded
> to improve developer workflow and automated checks on incoming
Hi RP,
Thanks, clear enough, here are the summary. For anyone who
cares about runqemu, please free to give your comments, I will
start working on it sooner.
1) Use python to replace of shell
2) Preserve the current command line options
3) Remove any machine knowledges out of runqemu scripts
4)
On Thu, 2016-06-23 at 16:43 +0800, Robert Yang wrote:
> On 06/23/2016 04:17 PM, Richard Purdie wrote:
> > On Tue, 2016-05-10 at 01:13 -0700, Robert Yang wrote:
> > Sorry about not responding to this before now. My concerns:
> >
> > a) The commandline structure is changing and I'm not sure I like
On 06/23/2016 11:16 AM, Chen Qi wrote:
'python' is added to RDEPENDS of systemd-ptest.
-RDEPENDS_${PN}-ptest += "gawk make perl bash xz \
+RDEPENDS_${PN}-ptest += "gawk make perl bash xz python\
This is not correct. Systemd is configured using --without-python, and
so the python scripts are
* format of bitbake tasks changed in:
2c88afb taskdata/runqueue: Rewrite without use of ID indirection
-ERROR: Task 4
(/OE/build/oe-core/openembedded-core/meta/recipes-devtools/rpm/sftp.bb,
do_fetch) failed with exit code '1'
+ERROR: Task
/openembedded-core-contrib
* [new branch] ChenQi/PU-20160623 -> origin/ChenQi/PU-20160623
error: 'refs/remotes/origin/marquiz/build-perf' exists; cannot create
'refs/remotes/origin/marquiz/build-perf/python-rewrite'
! [new branch] marquiz/build-perf/python-rewrite ->
origin/marquiz/b
During the extensible SDK installation process the final step is to
prepare the internal copy of the build system. This can take some time,
especially if you have SDK_EXT_TYPE set to "minimal" (downloading
sstate artifacts) and SDK_INCLUDE_PKGDATA set to "1" (restoring
pkgdata for world). To make
Use the new BB_SETSCENE_ENFORCE functionality to avoid having to run
bitbake twice on installing the extensible SDK - we can now do it all in
one invocation which not only takes less time, but we should also get
more meaningful errors for some types of failure, in particular where
downloading from
If BB_SETSCENE_ENFORCE is set to "1" and an sstate package fails to
download outside of the whitelist specified by
BB_SETSCENE_ENFORCE_WHITELIST, then fail immediately so you can tell
that the problem was caused by failing to restore the task from sstate.
Part of the implementation of [YOCTO
Use the new task progress functionality to report progress during
do_rootfs. This is a little coarse and ideally we would have some
progress within the installation section, but it's better than
nothing.
Signed-off-by: Paul Eggleton
---
meta/classes/image.bbclass
We don't want the value of this varflag in any signatures since it's
only there for the purpose of aiding display of task execution.
Signed-off-by: Paul Eggleton
---
meta/conf/bitbake.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
If we're building the extensible SDK we don't need to see the "Writing
locked sigs" message; it's only necessary when the user explicitly runs
bitbake -S none .
Signed-off-by: Paul Eggleton
---
meta/lib/oe/sstatesig.py | 10 --
1 file changed, 4
Show progress during build and extensible SDK installation.
I've often thought it would be nice if we could print progress information
for individual tasks so that you could get some idea of whether the task
is doing anything and how much longer it might take, and so I've been working
on a set of
Show progress through bitbake's standard terminal UI when checking for
shared state object availability, since this can take some time if there
are a large number of tasks to be executed and/or the network connection
is slow.
Part of the implementation for [YOCTO #5853].
Signed-off-by: Paul
cmake outputs percentage complete as part of its compilation process, so
we can enable BitBake's new progress scanning for do_compile here.
Signed-off-by: Paul Eggleton
---
meta/classes/cmake.bbclass| 1 +
With Python 3 we get a bytes object from the command output and not a
string, which gives some ugly formatting for error messages unless you
decode it first.
Signed-off-by: Paul Eggleton
---
meta/classes/testsdk.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2
In order to show the task progress during the extensible SDK
installation, knotty needs to know it is using a terminal it can
support the "interactive" mode on (i.e. ncurses can be used), which
means it needs access to the TERM variable value, so allow that
through into the cleaned environment
On 06/22/2016 06:00 PM, Martin Jansa wrote:
WARNING: e2fsprogs-1.43-r0 do_packagedata: QA Issue: Package version for
package e2fsprogs-locale-uk went backwards which would break package feeds
from (0:1.43.-r0.1 to 0:1.43-r0.0) [version-going-backwards]
Have you checked what opkg/rpm actually
On Thu, Jun 23, 2016 at 5:16 AM, Chen Qi wrote:
> Patches are rebased or removed for the latest version.
>
> 'python' is added to RDEPENDS of systemd-ptest.
>
> systemd-bootchart is now seprated from systemd, thus removing the
> related configuration items.
>
>
On Thu, Jun 23, 2016 at 3:23 AM, Alexander Kanavin
wrote:
> On 06/23/2016 11:16 AM, Chen Qi wrote:
>>
>> 'python' is added to RDEPENDS of systemd-ptest.
>> -RDEPENDS_${PN}-ptest += "gawk make perl bash xz \
>> +RDEPENDS_${PN}-ptest += "gawk make perl bash xz
On 06/23/2016 04:56 PM, Khem Raj wrote:
This is not correct. Systemd is configured using --without-python, and so
the python scripts are not added to the list of tests in the top level
Makefile.am. However they are still installed by the recipe - the correct
fix is to remove them from the test
On Thu, Jun 23, 2016 at 2:44 PM, Otavio Salvador
wrote:
> Depending on the module we use, the /run/lock may be required. This
> creates it as part of initial setup and thus makes it available for
> every sub module.
>
> Signed-off-by: Otavio Salvador
The mdev support relies on the mdev support inside busybox, which thus
builds the busybox-mdev package. Adding the runtime dependency ensures
its installation fails if mdev support is disabled.
Signed-off-by: Otavio Salvador
---
Changes in v2: None
They used to fail with PIE enabled, but no longer do.
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/security_flags.inc | 14 --
1 file changed, 14 deletions(-)
diff --git a/meta/conf/distro/include/security_flags.inc
Otherwise -native variants of recipes that use these classes don't get a proper
python[3]-native
dependency for some reason.
Signed-off-by: Alexander Kanavin
---
meta/classes/python3native.bbclass | 2 +-
meta/classes/pythonnative.bbclass | 2 +-
2 files
GNU make looks for "makefile" and "GNUmakefile" in addition to
"Makefile", so add these other names to the heuristic for detecting a
make-based project.
Signed-off-by: Nathan Lynch
---
scripts/lib/recipetool/create_buildsys.py | 2 +-
1 file changed, 1 insertion(+), 1
Signed-off-by: Khem Raj
---
.../{gstreamer1.0-libav_1.8.1.bb => gstreamer1.0-libav_1.8.2.bb}| 0
...er1.0-plugins-bad_1.8.1.bb => gstreamer1.0-plugins-bad_1.8.2.bb} | 4 ++--
...1.0-plugins-base_1.8.1.bb => gstreamer1.0-plugins-base_1.8.2.bb} | 4 ++--
Rich Felker (4):
fix undefined pointer arithmetic in CMSG_NXTHDR macro
fix a64l undefined behavior on ILP32 archs, wrong results on LP64 archs
avoid padding gaps in struct sockaddr_storage
remove comments on copyright status from UTF-8 implementation files
Szabolcs Nagy
On Fri, 24 Jun 2016 00:07:03 Paul Eggleton wrote:
> One result of this change is that you get the errors printed on the
> console during normal output rather than this going to the
> preparing_build_system.log file first. In OE-Core revision
> 227d2cbf9e0b8c35fa6644e3d72e0699db9607fa, we changed
Depending on the module we use, the /run/lock may be required. This
creates it as part of initial setup and thus makes it available for
every sub module.
Signed-off-by: Otavio Salvador
---
Changes in v2:
- New patch
On Wednesday, June 22, 2016 9:18:10 PM EDT Burton, Ross wrote:
> On 22 June 2016 at 19:24, Andreas Müller
>
> wrote:
> > Could we move vte to meta-oe to avoid further world blacklisting?
>
> This was the agreement in the other thread - Mark was going to restore the
The fuse-ld=bfd flag is not in the v4 patch, can you go back and try
the most recent one on the list?
Thanks...
On Thu, Jun 23, 2016 at 7:29 PM, Ting Liu wrote:
> Same issue on CentOS 6.7. Older gcc does not support -fuse-ld=bfd.
>
> -Ting
>
>> -Original Message-
>>
Same issue on CentOS 6.7. Older gcc does not support -fuse-ld=bfd.
-Ting
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
> Of Robert Yang
> Sent: Thursday, June 23, 2016 3:55 PM
> To:
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: Wednesday, June 22, 2016 7:30 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Hatle, Mark; Slater, Joseph; Khem Raj
> Subject: Re: [OE-core] [oe-core][PATCH 0/1] blacklist: add BPNBLACKLIST
45 matches
Mail list logo