From: Denys Dmytriyenko <denys@ti.com>
To: Kirk Sutherland <kirk.sutherland@apisensor.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: cmem.c fails to compile
Date: Mon, 30 Apr 2018 21:00:04 -0400 [thread overview]
Message-ID: <20180501010004.GA24094@edge> (raw)
In-Reply-To: <BN6PR04MB1044647DA248BB275122B4A0E48D0@BN6PR04MB1044.namprd04.prod.outlook.com>
Couple questions:
1. Any specific reason for gstreamer-ti? It has been deprecated long time ago.
2. Which gcc and what version? We've been using cmem for years w/o problems.
If using gcc from oe-core, is it the same branch - i.e. krogoth?
--
Denys
On Fri, Apr 27, 2018 at 05:36:43PM +0000, Kirk Sutherland wrote:
> Hi,
>
>
> I've been trying to build gstreamer-ti from the fido or krogoth branch of
> the gumstix/yocto manifest but ran into issues with the meta-ti parts. I can
> build the standard console and gumstix images just fine, but when try to
> bitbake gstreamer-ti I get:
>
>
> cmem.c:38:19: fatal error: stdio.h: no such file or directory
>
>
> I'm running it on a 32 bit system and as far as I can tell all the required
> libraries for gcc are there, it does make me think it could be related to
> this more recent issue with gcc
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129 but I'm not really sure
> what is happening here. Any pointers as to how to get this to work or what
> branch does work would be greatly appreciated.
next prev parent reply other threads:[~2018-05-01 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 17:36 cmem.c fails to compile Kirk Sutherland
2018-05-01 1:00 ` Denys Dmytriyenko [this message]
2018-05-01 13:49 ` Kirk Sutherland
2018-05-11 19:56 ` Kirk Sutherland
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=20180501010004.GA24094@edge \
--to=denys@ti.com \
--cc=kirk.sutherland@apisensor.com \
--cc=meta-ti@yoctoproject.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.