From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: cmake update broke mariadb
Date: Tue, 30 Jun 2015 12:00:26 +0200 [thread overview]
Message-ID: <mmtpbq$67d$2@ger.gmane.org> (raw)
In-Reply-To: <5591E548.8090706@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
akuster808 schreef op 30-06-15 om 02:39:
>
> Hello,
>
> eo-core commit f8661aa "cmake: Upgrade 2.8.12.2 -> 3.2.2" broke mariadb
> in meta-oe.
>
> DOes the person who updated cmake need to fix this or the person who is
> feeling the pain will be fixing it ?
I've been looking at this mariadb error and I've made no progress beyond
upgrading it to the latest 5.5.x, which shows the same cmake problem
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFVkmi6MkyGM64RGpERAmrsAJ0bCkH5omgOzpnB0dT8A6amMrYH6gCfU50x
ZObEl6kQHbI+QDeiui3GxfU=
=E2ZF
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: cmake update broke mariadb
Date: Tue, 30 Jun 2015 12:00:26 +0200 [thread overview]
Message-ID: <mmtpbq$67d$2@ger.gmane.org> (raw)
In-Reply-To: <5591E548.8090706@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
akuster808 schreef op 30-06-15 om 02:39:
>
> Hello,
>
> eo-core commit f8661aa "cmake: Upgrade 2.8.12.2 -> 3.2.2" broke mariadb
> in meta-oe.
>
> DOes the person who updated cmake need to fix this or the person who is
> feeling the pain will be fixing it ?
I've been looking at this mariadb error and I've made no progress beyond
upgrading it to the latest 5.5.x, which shows the same cmake problem
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFVkmi6MkyGM64RGpERAmrsAJ0bCkH5omgOzpnB0dT8A6amMrYH6gCfU50x
ZObEl6kQHbI+QDeiui3GxfU=
=E2ZF
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-06-30 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 0:39 cmake update broke mariadb akuster808
2015-06-30 9:44 ` [OE-core] " Burton, Ross
2015-06-30 9:44 ` Burton, Ross
2015-06-30 9:59 ` [OE-core] " Koen Kooi
2015-06-30 10:15 ` Burton, Ross
2015-06-30 10:15 ` [oe] " Burton, Ross
2015-06-30 10:32 ` [OE-core] " Stefan Herbrechtsmeier
2015-06-30 10:32 ` [oe] " Stefan Herbrechtsmeier
2015-06-30 12:53 ` [OE-core] " Koen Kooi
2015-06-30 12:53 ` [oe] " Koen Kooi
2015-06-30 19:34 ` [OE-core] " akuster808
2015-06-30 19:34 ` akuster808
2015-06-30 10:00 ` Koen Kooi [this message]
2015-06-30 10:00 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='mmtpbq$67d$2@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.