Re: [gccsdk] fontconfig build issue

Hi Lee

Thanks for the check. begs the Q of what it may be...

I did then try the --disable-docs which did bypass that issue, then grumble in the riscpkg stage:

add-riscpkg: Adding files for the RISC OS Packaging Project
add-riskpkg: Using Debian description
add-riscpkg: Setting filetypes...
add-riskpkg: Finished
Autobuilder: Packaging files
Autobuilder: Packaging as fontconfig-config
-rw-rw-rw- 1 jb jb 88085 Jun 29 19:00 /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig-config_2.11.0-1.zip
Autobuilder: Packaging as fontconfig
-rw-rw-rw- 1 jb jb 5704386 Jun 29 19:00 /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Fonts/fontconfig_2.11.0-1.zip
Autobuilder: Packaging as libfontconfig1-dev
-rw-rw-rw- 1 jb jb 860002 Jun 29 19:00 /home/jb/GCCSDK471/autobuilder/autobuilder_packages/Library/libfontconfig1-dev_2.11.0-1.zip
Autobuilder: Packaging as libfontconfig1
Autobuilder: package directory missing libfontconfig1
Package fontconfig: ***Failure***
Build for package "fontconfig" failed


Probably something simple that I'm missing, but the libfontconfig1 directory
doesn't exist in the package directory at this point.


IS there any AB type definition that brings in the native cc compiler, not the arm one?

Tanks

John

On 29/06/2015 16:50, Lee Noar wrote:

On 29/06/15 00:49, John Ballance wrote:

Hi

I'm trying to build fontconfig with the current cross compile toolset
(4.7.1) and the autobuilder

In the doc folder there is a thing called edit-sgml.c which should be
compiled for use on the host (compiling x86) machine, but is being
compiled into arm code.

Has anyone else met this, and more to the point, how in makefile or
makefile.am syntax do I oblige it to compile for local x86 rather than
crosscompile arm please

I've just tried a new build of fontconfig and it finished without error.
I suspect that you have a native package installed that I don't which
alters the behaviour of configure (ie, its absence on my machine makes
it skip the area you're having problems with).
Your best bet might be to configure with --disable-docs if you don't
mind not having the documentation. You would add this to AB_CONFLAGS
in setvars.

Lee.


_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK

--

Stop press! Just announced -

Most Trusted Broadband Provider in the 2014 Moneywise Customer Services Awards

For full details of see https://www.utilitywarehouse.co.uk/reviews?exref=095761

Intrigued? Call me

John Ballance C.Eng MIET - jwb@macpcrepair.co.uk - 07976 295923