On Tue, Jan 17, 2017 at 1:12 AM, Trevor Woerner wrote:
> Hi Paul,
>
> On Thu 2017-01-05 @ 09:59:16 PM, Paul Barker wrote:
>> Also, are you thinking of moving the -rt recipe to the 4.9 series when
>> upstream linux-raspberrypi declares that stable?
>
> I just want to confirm that 4.9 is going to be
Hi,
A couple of comments even though I'm coming late to the discussion.
So, from what I've understood from the above, the main issue with the
docker approach to building a yocto/oe image on the mac is that it was much
slower... Here's some numbers that don’t quite agree with that assertion:
I
Hi Paul,
On Thu 2017-01-05 @ 09:59:16 PM, Paul Barker wrote:
> Also, are you thinking of moving the -rt recipe to the 4.9 series when
> upstream linux-raspberrypi declares that stable?
I just want to confirm that 4.9 is going to be the next stable series? How do
we know 4.8 isn't going to be the
Thanks Ross,
I came to that conclusion too, and changes to the asterisk build system was
really always the most likely source of the problem. On the plus side, I have
learned a lot more about machine/processor configuration in the bsp layers
pursuing that dead end.
I went back through the a
+Khem
On Mon, Jan 16, 2017 at 4:40 PM, Burton, Ross wrote:
>
> On 16 January 2017 at 14:47, Chris Trobridge
> wrote:
>
>> Managed to get the actual compiler lines and the initial args are "-m32
>> -march=i586" but there is "-march=native" appended to the end of the
>> line.
>>
>> Looks like ast
From: Monserrat Sedeno
The new nightly-oe-build-perf-test buildset executes the
build-perf-test-wrapper.sh into a worker and publish the results to
specified folder by AB config.
When the performance script finish it sends an notifcation email to
yocto alias users, the worker machine needs to co
Sometimes is a good idea to could specify a machine to build via a build
property.
Signed-off-by: Aníbal Limón
---
.../site-packages/autobuilder/buildsteps/CreateAutoConf.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
a/lib/python2.7/site-packages/autobuilder
On 16 January 2017 at 14:47, Chris Trobridge
wrote:
> Managed to get the actual compiler lines and the initial args are "-m32
> -march=i586" but there is "-march=native" appended to the end of the line.
>
>
Looks like asterisk itself is adding -march=native, so you'll need to dig
through it's mak
On 16 January 2017 14:51:55 GMT+00:00, Gary Thomas wrote:
>On 2017-01-16 15:48, Gary Thomas wrote:
>> On 2017-01-16 08:26, Paul Barker wrote:
>>> As discussed recently on the list, we can just keep LTS versions now
>>> that v4.9 is available.
>>>
>>> I'm sending these so anyone who still needs v4.
Hi Chris,
there is a hint here how you can find out what gcc is actually using; you
could try with and without the -march=native:
http://en.chys.info/2010/04/what-exactly-marchnative-means/
On Mon, Jan 16, 2017 at 3:47 PM, Chris Trobridge wrote:
> the initial args are "-m32 -march=i586" but th
Hello list,
if I start the following command in a tmux window it doesn't work.
bitbake -c menuconfig linux-fslc
if I start this command in a extra gnome-terminal a new gnome-terminal
pops-up and I can configure my kernel related stuff.
in the poky /os-poky/meta/lib/oe/terminal.py there is some
On 2017-01-16 15:48, Gary Thomas wrote:
On 2017-01-16 08:26, Paul Barker wrote:
As discussed recently on the list, we can just keep LTS versions now
that v4.9 is available.
I'm sending these so anyone who still needs v4.7 or v4.8 can shout
'stop!' before we remove them.
Paul Barker (2):
linu
On 2017-01-16 08:26, Paul Barker wrote:
As discussed recently on the list, we can just keep LTS versions now
that v4.9 is available.
I'm sending these so anyone who still needs v4.7 or v4.8 can shout
'stop!' before we remove them.
Paul Barker (2):
linux-raspberrypi: Drop v4.7
linux-raspberr
Ok,
Rebuilt system the for i586 and asterisk is still the one program to fail,
still with that illegal andn instruction. So I can rule out the core2 tuning.
The compiler log is next to useless, as the asterisk build hides the command
lines but the makeopts files has the following, which seem
Whilst building libfdt on mingw32 is functional, building dtc for minw32
is not. This is due to dtc relying on certain POSIX functions as well as
not handling the MSVCRT printf formatting.
This change enables building and installing libfdt only for mingw32,
disabling the build of device-tree-compi
Relocate and package the dll's provided by libgcc in bindir. It is
convention that on mingw/windows dll files are installed into the
bindir, this is done to avoid issues with search paths and allows for
execution of binaries without the need to point at a libdir.
Signed-off-by: Nathan Rossi
---
The changes that are appended for '--enable-include=printf=yes' and
packaging of charset.alias and gthread-2.0.def are handled in oe-core.
Clean up these appends.
Signed-off-by: Nathan Rossi
---
recipes-core/glib-2.0/glib-2.0_%.bbappend | 3 ---
1 file changed, 3 deletions(-)
diff --git a/recip
Prevent glib-2.0 depending on bash indirectly due to the RDEPEND on
bash-completion. The bash dependency is undesirable due to bash
depending on POSIX compatibility (fork, etc) which is not provided by
MinGW but instead MSYS or CYGWIN.
The glib-2.0 configure does not allow for disabling of bash-co
Enable building of shared libs/dlls for gettext.
Signed-off-by: Nathan Rossi
---
recipes-core/gettext/gettext_0.19.%.bbappend | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-core/gettext/gettext_0.19.%.bbappend
b/recipes-core/gettext/gettext_0.19.%.bbappend
index efd
Add the 'secure-api' PACKAGECONFIG and enable it by default. The
'secure-api' feature enables the secure string functions that are
provided in the MS C Runtime e.g. "strerror_s".
These functions are needed for glib-2.0 compilation.
Signed-off-by: Nathan Rossi
---
recipes-devtools/mingw-w64/nati
From: Juro Bystricky
With the change of crosssdk to use SDK_SYS instead of SDK_ARCH, we need to
update
the recipe to match the changes in master.
[YOCTO #9281]
Signed-off-by: Juro Bystricky
---
recipes-devtools/mingw-w64/nativesdk-mingw-w64-runtime_3.1.0.bb | 2 +-
1 file changed, 1 insertio
This series is paired with a series that is sent for the oe-core meta
layer. That series depends on changes in this series and vice-versa. The
oe-core meta series can be reviewed via:
https://patchwork.openembedded.org/series/4800/
Additional information about this work can be read in the cover
Hi Joe,
On Thu, Jan 12, 2017 at 8:57 PM, Joe MacDonald
wrote:
>
> Hi guys,
>
> [Re: [meta-selinux] What's the point of refpolicy-minimum?] On 17.01.12
(Thu 12:57) wenzong fan wrote:
>
> > On 01/10/2017 10:48 PM, Joe MacDonald wrote:
> > >Wenzong / Shrikant,
> > >
> > >I thought I knew the answer
On 14 January 2017 at 19:45, Roger Smith wrote:
> Is Building Yocto project on a POSIX system, a desire for the Yocto
> project? It would allow support on all bsd UNIX’s including macOS
>
Making OE itself work isn't rocket science - fix a few Linuxisms in
bitbake, port pseudo to macOS.
The hard
On 2017-01-16 11:40, Burton, Ross wrote:
On 16 January 2017 at 04:29, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
* Any ideas how upgrading the X server now calls into openssl?
I've bisected this error down to the change in the X server
recipe to v1.19 from v1.18.4
$ grep
On 16 January 2017 at 04:29, Gary Thomas wrote:
> * Any ideas how upgrading the X server now calls into openssl?
>I've bisected this error down to the change in the X server
>recipe to v1.19 from v1.18.4
>
$ grep ssl *
xserver-xorg.inc:XORG_CRYPTO ??= "openssl"
xserver-xorg.inc:PACKAGECO
In trying to debug my Xorg server problem, I've installed a
number of xxx-dbg packages (using IPK/OPKG). One thing that
I noticed is that for some of them, e.g. xserver-xorg, I got
a full source tree which works great for debugging with GDB.
Some other packages, e.g. xf86-video-imxfb-vivante whic
Thanks Leon,
I agree it is probably an unrelated coincidence. I am also using morty.
I don't have the logs around any more but the logs had -march=core2
-mtune-core2 -m32, which was correct for the build. I did wonder whether the
asterisk autoconf was too clever but I think in my case it ma
Hello Chris,
Probably unrelated, but yesterday my krogoth build failed on an Atom
*host/build* system. I was just about to debug this when I saw your email.
The configure stage of gmp-native decided to choose -march=k8 and -mtune=k8
-m64. I am debugging this currently.
Maybe check if the asterix
This arose building asterisk switching from 13.7 to 13.11+.
The executable core dumps immediately with an illegal instruction instruction,
which gdb reported as 'andn'. This is part of BMI1, which was introduced with
Haswell. I am targeting a (32-bit) Z5xx Atom processor, which predates this
30 matches
Mail list logo
