Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eial Czerwacki <eial@scalemp.com>
To: buildroot@busybox.net
Subject: [Buildroot] could not read symbols: Bad value error on musl based buildroot env on rpi2 config.
Date: Mon, 18 Jan 2016 08:23:46 +0200	[thread overview]
Message-ID: <569C84F2.1050309@scalemp.com> (raw)
In-Reply-To: <569BFB04.4050000@mind.be>

Greetings,

the pastebin can be found at http://paste.ubuntu.com/14565509/

what makes it a bit weirder is that on my 64 bit gentoo machine (this is
a 32 bit ubuntu 12.04 machine) it compiles well.

On 01/17/2016 10:35 PM, Arnout Vandecappelle wrote:
> On 17-01-16 16:42, Eial Czerwacki wrote:
>> Greetings,
>>
>> I'm trying to create a musl base env for my rpi2 and I'm getting the
>> below failure.
>>
>> /usr/bin/ld: /usr/local/lib/libpython2.7.a(abstract.o): relocation
>  This is bad, because it's trying to use your installed python while building
> buildroot's host-python... This error happens while compiling host-python,
> right? You didn't show the last bit of the output.
>
>  Can you pastebin output/build/host-python-2.7.11/config.log?
>
>  (Note for others on the list: I suspect host-python is built for xcb-proto and
> libxcb.)
>
>  Regards,
>  Arnout
>
>> R_X86_64_32 against `.rodata.str1.8' can not be used when making a
>> shared object; recompile with -fPIC
>> /usr/local/lib/libpython2.7.a: could not read symbols: Bad value
>> collect2: ld returned 1 exit status
>>
>> Python build finished, but the necessary bits to build these modules
>> were not found:
>> _tkinter           bsddb185           dl             
>> imageop            sunaudiodev                       
>> To find the necessary bits, look in setup.py in detect_modules() for the
>> module's name.
>>
>>
>> Failed to build these modules:
>> _bisect            _codecs_iso2022    _collections   
>> _csv               _ctypes            _ctypes_test   
>> _elementtree       _functools         _hashlib       
>> _heapq             _hotshot           _io            
>> _json              _locale            _lsprof        
>> _multibytecodec    _multiprocessing   _random        
>> _socket            _ssl               _struct        
>> _testcapi          array              audioop        
>> binascii           cmath              cPickle        
>> crypt              cStringIO          datetime       
>> fcntl              future_builtins    grp            
>> itertools          linuxaudiodev      math           
>> mmap               operator           parser         
>> pyexpat            readline           resource       
>> select             spwd               strop          
>> syslog             termios            time           
>> unicodedata        zlib                              
>>
>> make[1]: *** [sharedmods] Error 1
>>
>> my config can be found here: http://paste.ubuntu.com/14543009/
>>
>> is it possible I'm having a bitness issue on the system? the machine I'm
>> using to compile is 64 bit but the machine on which the fs exists is 32 bit.
>> any ideas how to fix it?
>>
>> Thanks.
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>

  reply	other threads:[~2016-01-18  6:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 15:42 [Buildroot] could not read symbols: Bad value error on musl based buildroot env on rpi2 config Eial Czerwacki
2016-01-17 20:35 ` Arnout Vandecappelle
2016-01-18  6:23   ` Eial Czerwacki [this message]
2016-01-18  8:59     ` Arnout Vandecappelle
2016-01-18  9:09       ` Eial Czerwacki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=569C84F2.1050309@scalemp.com \
    --to=eial@scalemp.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox