Dan McMahill wrote:
> DJ Delorie wrote:
>>> /usr/bin/ld: footprintupdate.o: relocation R_X86_64_32 against `a
>>> local symbol' can not be used when making a shared object; recompile
>>> with -fPIC
>> Shared libraries should ALWAYS be built with -fpic or -fPIC. The i386
>> gets away without it bec
DJ Delorie wrote:
>> /usr/bin/ld: footprintupdate.o: relocation R_X86_64_32 against `a
>> local symbol' can not be used when making a shared object; recompile
>> with -fPIC
>
> Shared libraries should ALWAYS be built with -fpic or -fPIC. The i386
> gets away without it because the developers got
> /usr/bin/ld: footprintupdate.o: relocation R_X86_64_32 against `a
> local symbol' can not be used when making a shared object; recompile
> with -fPIC
Shared libraries should ALWAYS be built with -fpic or -fPIC. The i386
gets away without it because the developers got tired of answering
questio
Cliff Brake wrote:
> On Sat, May 24, 2008 at 1:02 PM, Dean Ferreyra <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> I've written a PCB plug-in that lets you replace existing footprints
>> in your layout with updated footprints. It's described here:
>> http://www.bourbonstreetsoftware.com/PCBFootprintUp
On Sat, May 24, 2008 at 1:02 PM, Dean Ferreyra <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've written a PCB plug-in that lets you replace existing footprints
> in your layout with updated footprints. It's described here:
> http://www.bourbonstreetsoftware.com/PCBFootprintUpdatePlugIn.html .
>
> I'm
Hello,
I've written a PCB plug-in that lets you replace existing footprints
in your layout with updated footprints. It's described here:
http://www.bourbonstreetsoftware.com/PCBFootprintUpdatePlugIn.html .
I'm not sure how useful this will be generally since everyone's
workflow is different,
6 matches
Mail list logo
