Jump to content


Photo

Tuxcom missing from feeds


  • Please log in to reply
28 replies to this topic

Re: Tuxcom missing from feeds #21 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 6 August 2014 - 20:40

I see this:

mipsel-oe-linux-gcc  -mel -mabi=32 -mhard-float -march=mips32 --sysroot=/media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 -DHAVE_CONFIG_H -I. -I./include   -Os -pipe -g -feliminate-unused-debug-types -I/usr/include/freetype2 -Os -pipe -g -feliminate-unused-debug-types -c -o tuxcom.o tuxcom.c

cc1: warning: include location "/usr/include/freetype2" is unsafe for cross-compilation [-Wpoison-system-directories]
| In file included from tuxcom.c:25:0:
| tuxcom.h:50:22: fatal error: ft2build.h: No such file or directory
|  #include <ft2build.h>

 


But in mentioned sysroot /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000/usr/include/freetype2 the file ft2build.h is present...

But the warning says there is a problem...


Edited by betacentauri, 6 August 2014 - 20:40.

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Tuxcom missing from feeds #22 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 6 August 2014 - 20:46

With

 

mipsel-oe-linux-gcc -mel -mabi=32 -mhard-float -march=mips32 --sysroot=/media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 -DHAVE_CONFIG_H -I. -I./include -Os -pipe -g -feliminate-unused-debug-types -I/media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000/usr/include/freetype2 -Os -pipe -g -feliminate-unused-debug-types -c -o tuxcom.o tuxcom.c

it works.

But how to change it?


Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Tuxcom missing from feeds #23 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 6 August 2014 - 21:03

Problem is that 

/usr/bin/freetype-config --cflags

on build host is executed. This returns

-I/usr/include/freetype2

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Tuxcom missing from feeds #24 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 6 August 2014 - 21:48

Problem is that 

/usr/bin/freetype-config --cflags

on build host is executed. This returns

-I/usr/include/freetype2

Yes I saw all those things happening.

 

The latest autotools in openembedded started to be weird with things they did not before very good . I gues that maintainers wan't the packag developpers to make a descent configure.ac and make.am file. At this time they are removing a lot off things which will forced serious changes on used packages. Before there where som genious guys who developped great util bbclass routins. Now Some off the maintainers is remving them al be all.  The result is every day more unbuldable packages and really needed ones. the name of that guy is

 

Removing off autoconf patch enforcing foriegn  very bad idea done by Ross Burtun singed Richard purdie

 

also removing the binconfig

 

http://cgit.openembe...b251884c1c05061

 

 

and a lot more those are the culprits . They perhaps a goal ??? Till now I only see ver very reduced suppordt. autoconf failes the longer the more.


Edited by christophecvr, 6 August 2014 - 21:53.


Re: Tuxcom missing from feeds #25 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 6 August 2014 - 22:47

I see this:

mipsel-oe-linux-gcc  -mel -mabi=32 -mhard-float -march=mips32 --sysroot=/media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 -DHAVE_CONFIG_H -I. -I./include   -Os -pipe -g -feliminate-unused-debug-types -I/usr/include/freetype2 -Os -pipe -g -feliminate-unused-debug-types -c -o tuxcom.o tuxcom.c

cc1: warning: include location "/usr/include/freetype2" is unsafe for cross-compilation [-Wpoison-system-directories]
| In file included from tuxcom.c:25:0:
| tuxcom.h:50:22: fatal error: ft2build.h: No such file or directory
|  #include <ft2build.h>

 


But in mentioned sysroot /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000/usr/include/freetype2 the file ft2build.h is present...

But the warning says there is a problem...

yes th include should be /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 /ur/include/libfreetype6



Re: Tuxcom missing from feeds #26 radxnl

  • Senior Member
  • 1,527 posts

+57
Good

Posted 6 August 2014 - 22:49

nah ;)

 

i just pushed a fix on both our git and svn to handle it



Re: Tuxcom missing from feeds #27 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 6 August 2014 - 22:58

Interesting. Thanks!
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: Tuxcom missing from feeds #28 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 7 August 2014 - 07:51

I see this:

mipsel-oe-linux-gcc  -mel -mabi=32 -mhard-float -march=mips32 --sysroot=/media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 -DHAVE_CONFIG_H -I. -I./include   -Os -pipe -g -feliminate-unused-debug-types -I/usr/include/freetype2 -Os -pipe -g -feliminate-unused-debug-types -c -o tuxcom.o tuxcom.c

cc1: warning: include location "/usr/include/freetype2" is unsafe for cross-compilation [-Wpoison-system-directories]
| In file included from tuxcom.c:25:0:
| tuxcom.h:50:22: fatal error: ft2build.h: No such file or directory
|  #include <ft2build.h>

 


But in mentioned sysroot /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000/usr/include/freetype2 the file ft2build.h is present...

But the warning says there is a problem...

yes th include should be /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000 /ur/include/libfreetype6

I meant the include should look in /media/linux/enigma2/openpli4/openpli-oe-core/build/tmp/sysroots/et8000/usr/include/libfreetype2

 

The files are present by me for dm8000 and also for vuduo2



Re: Tuxcom missing from feeds #29 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 7 August 2014 - 08:01

Here it does work ok with latest master pli40

 

tuxcom compile log. Clealy can be seen that it used target's includes and target's libs. No Wpoison here

 

 

Attached Files




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users