Bug 103385

Summary: Cross compilation fails with undefined reference
Product: Mesa Reporter: bkarthikk93
Component: OtherAssignee: mesa-dev
Status: RESOLVED WONTFIX QA Contact: mesa-dev
Severity: major    
Priority: medium    
Version: 13.0   
Hardware: ARM   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description bkarthikk93 2017-10-21 09:17:10 UTC
I have been trying to cross compile Mesa 13.0.6 and 12.0.6 for an arm platform. Both compilation is failing with the following error 

 Making all in gbm
make[3]: Entering directory '/opt/qt/qt5.9.1arm_source/dependencies/mesa/mesa-13.0.6/src/gbm'
  CCLD     libgbm.la
../../src/loader/.libs/libloader.a(libxmlconfig_la-xmlconfig.o): In function `__getProgramName':
xmlconfig.c:(.text+0x78): undefined reference to `__progname'
collect2: error: ld returned 1 exit status
Makefile:847: recipe for target 'libgbm.la' failed
make[3]: *** [libgbm.la] Error 1
Comment 1 bkarthikk93 2017-10-21 09:40:16 UTC
*** Bug 103386 has been marked as a duplicate of this bug. ***
Comment 2 Timothy Arceri 2018-08-21 01:59:19 UTC
(In reply to bkarthikk93 from comment #0)
> I have been trying to cross compile Mesa 13.0.6 and 12.0.6 for an arm
> platform. Both compilation is failing with the following error 
> 
>  Making all in gbm
> make[3]: Entering directory
> '/opt/qt/qt5.9.1arm_source/dependencies/mesa/mesa-13.0.6/src/gbm'
>   CCLD     libgbm.la
> ../../src/loader/.libs/libloader.a(libxmlconfig_la-xmlconfig.o): In function
> `__getProgramName':
> xmlconfig.c:(.text+0x78): undefined reference to `__progname'
> collect2: error: ld returned 1 exit status
> Makefile:847: recipe for target 'libgbm.la' failed
> make[3]: *** [libgbm.la] Error 1

You need to make sure correct support is offered in xmlconfig.c for your platform/compiler. Patches welcome and can be sent to the mesa-dev mailing list. 

For now I'm going to close this bug as wont fix.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.