cmem.c fails to compile

cmem.c fails to compile

[Kirk Sutherland]

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

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.

IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.

[-- Attachment #2: Type: text/html, Size: 1952 bytes --]

Re: cmem.c fails to compile

[Denys Dmytriyenko]

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.

Re: cmem.c fails to compile

[Kirk Sutherland]

[-- Attachment #1: Type: text/plain, Size: 2895 bytes --]

  1.  I'm porting firmware written for another board using the DM3730 and it uses dsplink, I'd rather not have to rewrite it to whatever TI is using now, but I would take an alternative if necessary.
  2.  I'm pulling from krogoth, although I'm not entirely sure what version of gcc it is since I see a version of gcc in a bunch of tmp folders that bitbake creates. I've also tried fido with the same results. I'm using the repo script as described in the yocto-manifest page to sync everything.

________________________________
From: Denys Dmytriyenko <denys@ti.com>
Sent: Monday, April 30, 2018 9:00:04 PM
To: Kirk Sutherland
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] cmem.c fails to compile

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
70129 – [6 Regression] stdlib.h: No such file or directory ...<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129>
gcc.gnu.org
GCC Bugzilla – Bug 70129 [6 Regression] stdlib.h: No such file or directory when using -isystem /usr/include Last modified: 2018-02-14 04:04:17 UTC



> what is happening here. Any pointers as to how to get this to work or what
> branch does work would be greatly appreciated.
IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.
IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.

[-- Attachment #2: Type: text/html, Size: 6296 bytes --]

Re: cmem.c fails to compile

[Kirk Sutherland]

[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]

Any update on possible resolutions?

________________________________
From: Kirk Sutherland
Sent: Tuesday, May 1, 2018 9:49:36 AM
To: Denys Dmytriyenko
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] cmem.c fails to compile


  1.  I'm porting firmware written for another board using the DM3730 and it uses dsplink, I'd rather not have to rewrite it to whatever TI is using now, but I would take an alternative if necessary.
  2.  I'm pulling from krogoth, although I'm not entirely sure what version of gcc it is since I see a version of gcc in a bunch of tmp folders that bitbake creates. I've also tried fido with the same results. I'm using the repo script as described in the yocto-manifest page to sync everything.

________________________________
From: Denys Dmytriyenko <denys@ti.com>
Sent: Monday, April 30, 2018 9:00:04 PM
To: Kirk Sutherland
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] cmem.c fails to compile

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
70129 – [6 Regression] stdlib.h: No such file or directory ...<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129>
gcc.gnu.org
GCC Bugzilla – Bug 70129 [6 Regression] stdlib.h: No such file or directory when using -isystem /usr/include Last modified: 2018-02-14 04:04:17 UTC



> what is happening here. Any pointers as to how to get this to work or what
> branch does work would be greatly appreciated.
IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.
IMPORTANT NOTICE FROM API: This communication, including any attachments, contains information that may be confidential or privileged and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please contact the sender immediately and delete this message. Any unauthorized disclosure, copying or distribution of this message is strictly prohibited.

[-- Attachment #2: Type: text/html, Size: 7054 bytes --]