On 28/02/20 11:34 am, Joshua Watt wrote:
On 2/27/20 4:29 PM, Douglas Royds wrote:
On 28/02/20 10:49 am, Joshua Watt wrote:
On 2/27/20 3:22 PM, Douglas Royds wrote:
On 28/02/20 5:45 am, Joshua Watt wrote:
On 2/27/20 9:01 AM, Joshua Watt wrote:
On 2/26/20 11:46 PM, Douglas Royds wrote:
On 28/02/20 10:49 am, Joshua Watt wrote:
On 2/27/20 3:22 PM, Douglas Royds wrote:
On 28/02/20 5:45 am, Joshua Watt wrote:
On 2/27/20 9:01 AM, Joshua Watt wrote:
On 2/26/20 11:46 PM, Douglas Royds wrote:
On 26/02/20 4:53 am, Jacob Kroon wrote:
On 2/24/20 8:25 AM, Jacob Kroon wrote:
Hi
On 28/02/20 5:45 am, Joshua Watt wrote:
On 2/27/20 9:01 AM, Joshua Watt wrote:
On 2/26/20 11:46 PM, Douglas Royds wrote:
On 26/02/20 4:53 am, Jacob Kroon wrote:
On 2/24/20 8:25 AM, Jacob Kroon wrote:
Hi Douglas,
You updated a comment in reproducible_build.bbclass, commit
On 26/02/20 4:53 am, Jacob Kroon wrote:
On 2/24/20 8:25 AM, Jacob Kroon wrote:
Hi Douglas,
You updated a comment in reproducible_build.bbclass, commit
e7b891b76954c784f5a93bd0a1c91315673ce40d:
-# Once the value of SOURCE_DATE_EPOCH is determined, it is stored
in the recipe's ${SDE_FILE}.
On 4/11/19 11:29 PM, Richard Purdie wrote:
On Mon, 2019-11-04 at 17:52 +1300, Douglas Royds via Openembedded-core
wrote:
Mostly just longer (and hopefully more meaningful) variable names.
"Mostly" - what else is in there?
Readability changes only.
* Longer variable names
* Rew
Mostly just longer (and hopefully more meaningful) variable names.
Signed-off-by: Douglas Royds
---
meta/classes/insane.bbclass | 81 +++--
1 file changed, 42 insertions(+), 39 deletions(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
Mostly just longer (and hopefully more meaningful) variable names.
Signed-off-by: Douglas Royds
---
meta/classes/insane.bbclass | 84 -
1 file changed, 45 insertions(+), 39 deletions(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
We don't have a compiler, so no icecc.
Silences a spew of warnings of the form:
do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX
Signed-off-by: Douglas Royds
---
meta/classes/icecc.bbclass | 4
1 file changed, 4 insertions(+)
diff --git a/meta/classes/icecc.bbclass
By exporting ICECC_CC, ICECC_CXX, and ICECC_VERSION in a wrapper-script,
and putting this wrapper-script in the PATH, the Makefiles generated by CMake or
the autotools are able to function correctly outside of bitbake.
This provides a convenient developer workflow in which the
An error in my analysis below: We *do* delete the dependency files in
the in-tree build case as well. The side-effect is masked in both
in-tree and out-of-tree build cases except here at Tait, where we don't
delete the entire build at configure time, due to a 20min+ rebuild time,
even with the
This commit is having an unintended side-effect in the -native (and
probably nativesdk) case.
In the target build, $includedir is normally /usr/include,
fully-qualified. This path is already in CMake's list of implicit
include directories, and we don't include any header files from the
build
On 2/07/19 3:58 AM, Joshua Watt wrote:
1. Testing RPM and IPK package formats. I think RPMs will be pretty
easy; IPKs might be more challenging since AFAIK the tools that make
them don't generate reproducible output to begin with.
This has not been my experience. I have been building
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthough */
comments in switch statements that normally prevent an implicit-fallthrough
warning, see https://github.com/icecc/icecream/issues/419
On 11/06/19 4:57 PM, Adrian Bunk wrote:
On Tue, Jun 11, 2019 at 03:12:09PM +1200, Douglas Royds via Openembedded-core
wrote:
On 11/06/19 3:05 PM, Kang Kai wrote:
On 2019/6/11 上午11:04, Douglas Royds wrote:
On 11/06/19 2:46 PM, Kang Kai wrote:
...
Use option '-M' of git format-patch may
On 11/06/19 3:05 PM, Kang Kai wrote:
On 2019/6/11 上午11:04, Douglas Royds wrote:
On 11/06/19 2:46 PM, Kang Kai wrote:
On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:
Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly
On 11/06/19 2:46 PM, Kang Kai wrote:
On 2019/6/11 上午9:57, Douglas Royds via Openembedded-core wrote:
Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.
icecc preprocesses source files locally before shipping them off
Please disregard this one, I've sent a recipe update to pick up the new
--disable-werror configure option.
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Upstream json-c haven't made a release since March 2018.
Adopt the current HEAD revision, pulling it directly from git.
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthough */
comments in
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthrough
*/
comments in switch statements that normally prevent the implicit-fallthrough
warning.
Rather than turning off -Werror by patching
really need to get
around to updating it
On 6/6/19 4:03 PM, Douglas Royds via Openembedded-core wrote:
I struggled to find a solution that would work in the -native case,
as we need to support gcc as old as 5.4 (Ubuntu 16.04).
The problem is somewhat specific to json-c, as -Werror is hard-coded
that the gcc upgrade introducing that warning
caused I'll be *very* surprised if this problem is limited to json-c.
Could the icecc class forcibly disable that warning instead?
Ross
On Thu, 6 Jun 2019 at 03:06, Douglas Royds via Openembedded-core
wrote:
icecc preprocesses source files locally
Please disregard this one, I have submitted a newer patch under a new
subject-line:
json-c: Disable icecc to avoid implicit-fallthrough warning as error
On 6/06/19 1:13 PM, Douglas Royds wrote:
icecc preprocesses source files locally before shipping them off to be compiled
on remote
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthrough
*/
comments in switch statements that normally prevent the implicit-fallthrough
warning.
Rather than turning off -Werror by patching
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthrough
*/
comments in switch statements that normally prevent the implicit-fallthrough
warning. Rather than turning off -Werror completely, just
icecc preprocesses source files locally before shipping them off to be compiled
on remote hosts. This preprocessing removes comments, including /* fallthough */
comments in switch statements that normally prevent the implicit-fallthrough
warning. Rather than turning off -Werror completely, just
On 14/05/19 6:41 PM, Martin Hundebøll wrote:
On 14/05/2019 08.16, Douglas Royds via Openembedded-core wrote:
Can anyone explain why I appear on patchwork as "Andrii Bordunov via
Openembedded-core"?
Yes.
Because the DMARC policy for your domain is "quarantine":
% dig
Can anyone explain why I appear on patchwork as "Andrii Bordunov via
Openembedded-core"?
See https://patchwork.openembedded.org/series/17604/
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
Line lengths, remove duplication, and use the PYTHON variable provided by
pythonnative.bbclass.
Coincidentally fixes a dormant defect in distutils3.bbclass in which we were
sedding for STAGING_BINDIR_NATIVE/python-python3/python3.
Signed-off-by: Douglas Royds
---
meta/classes/distutils.bbclass
The python distutils generate a python wrapper script for each package,
containing shebang lines pointing to the python executable.
In our case, this is a fully-qualified path to python-native in the
recipe-sysroot-native.
Ubuntu 18.04 restricts the useful length of the shebang line to 125
The python distutils generate a python wrapper script for each package,
containing shebang lines pointing to the python executable.
In our case, this is a fully-qualified path to python-native in the
recipe-sysroot-native.
Ubuntu 18.04 restricts the useful length of the shebang line to 125
The python distutils generate a python wrapper script for each package.
These python scripts have shebang lines pointing to the python executable.
In our case, this is a fully-qualified path to python-native in the
recipe-sysroot-native.
Ubuntu 18.04 restricts the useful length of the shebang
31 matches
Mail list logo
