Comment 9 for bug 1113307
Revision history for this message
| Wayne Stambaugh (stambaughw) wrote Re: [Bug 1113307] Re: Kicad build with scripting options (Debian Wheezy/Testing) | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On 2/11/2013 9:05 PM, Dick Hollenbeck wrote:
> On 02/11/2013 06:59 PM, Wayne Stambaugh wrote:
>> I just compiled this on 64 bit Debian/Wheezy without any issues. I used
>> ipython and imported pcbnew without any problems. Try running make
>> clean or completely rebuilding KiCad. There may be some issues since
>> Boost was just updated to 1.53.
>>
>
>
> If you need some fall back theory, consider this as such (since I did not check the
> CMakeLists.txt file about this):
>
>
> This could be a difference in binutils versions, and the error message may actually be
> correct.
>
> On x86_64 platforms any objects going into a DSO should be compiled with
> -fPIC.
>
> Not so important on x86.
>
> In any case since this code is not called from python, it has not blown up yet, the
> 3d-viewer is never called.
> Obviously some of the code in _pcbnew.so is compiled correctly, otherwise it would have
> crashed.
>
> Binutils is just giving us an early warning.
>
The -fPIC option is set when compiling with GCC on Linux. I'm wondering
if Oliver's change from python 2.6 to python 2.7 between builds had
anything to do with it. I compiled and linked against python 2.7.3
without any problems including the change over to Boost 1.53. Python
2.7.3 is the current default in Debian Wheezy.