[winswitch] error on build

Antoine Martin antoine at nagafix.co.uk
Sun Feb 26 06:08:47 GMT 2017 

On 25/02/17 23:11, Michael Durkin via shifter-users wrote:
> humm ....
> 
> says to use -fPIC, but it is included in the compile ...
Please see the link I have already posted:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448

Here's a direct quote:
"non-PIC shared libraries were never really deliberately supported for
ARM, they just worked by coincidence"

Cheers
Antoine

> 
> building 'xpra.codecs.libav_common.av_log' extension
> arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC
> -I/usr/local/include -I/usr/include/python2.7 -c
> xpra/codecs/libav_common/av_log.c -o
> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall -Werror
> -Wno-error=strict-prototypes -fPIC
> arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
> -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g
> -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g
> -fstack-protector-strong -Wformat -Werror=format-security
> -Wl,-Bsymbolic-functions -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g
> -fstack-protector-strong -Wformat -Werror=format-security
> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o
> -L/usr/local/lib -lavutil -lm -o
> build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall
> /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation
> R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when making
> a shared object; recompile with -fPIC
> /usr/local/lib/libavutil.a: error adding symbols: Bad value
> collect2: error: ld returned 1 exit status
> error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
> 
> 
> On Sat, Feb 25, 2017 at 8:08 AM, Michael Durkin <kc7noa at gmail.com> wrote:
> 
>> does that force usage of internal (that comes with xpra) codec's ?
>>
>> On Fri, Feb 17, 2017 at 8:38 PM, Antoine Martin <antoine at nagafix.co.uk>
>> wrote:
>>
>>> Please always keep the list CCed.
>>>
>>> On 18/02/17 01:43, Michael Durkin wrote:
>>>> ok, this error is over my head ...
>>>>
>>>> building 'xpra.codecs.libav_common.av_log' extension
>>>> arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
>>>> -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2
>>>> -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC
>>>> -I/usr/local/include -I/usr/include/python2.7 -c
>>>> xpra/codecs/libav_common/av_log.c -o
>>>> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o -Wall
>>>> -Werror -Wno-error=strict-prototypes -fPIC
>>>> arm-linux-gnueabihf-gcc -pthread -shared -Wl,-O1
>>>> -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro
>>>> -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
>>>> -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat
>>>> -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro
>>>> -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat
>>>> -Werror=format-security
>>>> build/temp.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.o
>>>> -L/usr/local/lib -lavutil -lm -o
>>>> build/lib.linux-armv7l-2.7/xpra/codecs/libav_common/av_log.so -Wall
>>>> /usr/bin/ld: /usr/local/lib/libavutil.a(log.o): relocation
>>>> R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when
>>>> making a shared object; recompile with -fPIC
>>>> /usr/local/lib/libavutil.a: error adding symbols: Bad value
>>>> collect2: error: ld returned 1 exit status
>>>> error: command 'arm-linux-gnueabihf-gcc' failed with exit status 1
>>> I think someone hit this error before, but I can't remember the details.
>>> This is a toolchain problem, you will need to get someone from Odroid to
>>> help you here. This looks relevant:
>>> https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/503448
>>>
>>> Or just disable the ffmpeg based codecs (and maybe others too):
>>> ./setup.py --without-dec_avcodec2 --without-csc_swcale
>>> --without-enc_ffmpeg
>>>
>>> Cheers
>>> Antoine
>>>
>>>
>>>
>>>>
>>>>
>>>> On Fri, Feb 17, 2017 at 9:44 AM, Michael Durkin <kc7noa at gmail.com
>>>> <mailto:kc7noa at gmail.com>> wrote:
>>>>
>>>>     Every thing on that page is installed .. or was already part of the
>>>>     Ubuntu 16.04 HardKernel image ...
>>>>
>>>>     hit this error ...
>>>>
>>>>     error: implicit declaration of function 'avcodec_receive_frame'
>>>>
>>>>     humm .. not quite an error, just not ffmpeg V3 ....
>>>>     Im not sure what would happen if i remove ffmpeg to anything else
>>> ...
>>>>     Ill try to build ffmpeg from svn/git ...
>>>>
>>>>     On Thu, Feb 16, 2017 at 10:57 PM, Antoine Martin via shifter-users
>>>>     <shifter-users at lists.devloop.org.uk
>>>>     <mailto:shifter-users at lists.devloop.org.uk>> wrote:
>>>>
>>>>         On 17/02/17 13:26, Michael Durkin via shifter-users wrote:
>>>>         > Not sure if this is a but yet .. probably more of a
>>> Odroid-X2/Ubuntu16.04
>>>>         > fresh install issue ..
>>>>         >
>>>>         > found gcc version: 5.4.0
>>>>         > Traceback (most recent call last):
>>>>         >   File "setup.py", line 2449, in <module>
>>>>         >     ffmpeg_pkgconfig = pkgconfig("libavcodec", "libavformat")
>>>>         >   File "setup.py", line 688, in exec_pkgconfig
>>>>         >     raise Exception("ERROR: cannot find a valid pkg-config
>>> entry for %s
>>>>         > using PKG_CONFIG_PATH=%s" % (" or ".join(options),
>>>>         > os.environ.get("PKG_CONFIG_PATH", "(empty)")))
>>>>         > Exception: ERROR: cannot find a valid pkg-config entry for
>>> libavformat
>>>>         > using PKG_CONFIG_PATH=(empty)
>>>>         You need the libavformat development headers and pkg-config
>>> file.
>>>>         I have added more details here:
>>>>         https://www.xpra.org/trac/wiki/Building/Debian
>>>>         <https://www.xpra.org/trac/wiki/Building/Debian>
>>>>
>>>>         Cheers
>>>>         Antoine
>>>>
>>>>         >
>>>>         > im still investigating ....
>>>>         > _______________________________________________
>>>>         > shifter-users mailing list
>>>>         > shifter-users at lists.devloop.org.uk
>>>>         <mailto:shifter-users at lists.devloop.org.uk>
>>>>         > http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>>>>         <http://lists.devloop.org.uk/mailman/listinfo/shifter-users>
>>>>         >
>>>>
>>>>         _______________________________________________
>>>>         shifter-users mailing list
>>>>         shifter-users at lists.devloop.org.uk
>>>>         <mailto:shifter-users at lists.devloop.org.uk>
>>>>         http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>>>>         <http://lists.devloop.org.uk/mailman/listinfo/shifter-users>
>>>>
>>>>
>>>>
>>>
>>>
>>
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
>

More information about the shifter-users mailing list