Still not quite ready to call this solved even though I got the "why"...
f2py will let LDFLAGS override the default built-in linker flags from
"linker_exe" and "linker_so". I would think at a minimum you would want it
as an append, not an override if not outright ignore the environment
variables f
Ok, I figured out the problem but not WHY it's a problem but basically it
doesn't like the linker flag "-Wl,-z,relro". I actually had to patch the
makefile for this so it wouldn't get applied to the f2py command but
apparently it was still casing a linker issue for some reason.
The workaround (I w
On Tue, Jun 10, 2014 at 11:07 AM, Andrew Schultz
wrote:
> Richard Shaw wrote:
>
>> /usr/lib/gcc/x86_64-redhat-linux/4.8.2/../../../../lib64/crt1.o: In
>> function `_start':
>> (.text+0x20): undefined reference to `main'
>> collect2: error: ld returned 1 exit status
>> rmbadname1: Replacing "len"
Richard Shaw wrote:
/usr/lib/gcc/x86_64-redhat-linux/4.8.2/../../../../lib64/crt1.o: In
function `_start':
(.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status
rmbadname1: Replacing "len" with "len_bn".
/usr/lib/gcc/x86_64-redhat-linux/4.8.2/../../../../lib64/crt
Does anyone have a favorite method of figuring out what build flags are
causing an issue?
I'm trying to package WSPR[1] for the ham radio sig. It is autotools based
and when I use %configure the build fails but when I just use plain
configure it succeeds. It uses gfortran and f2py extensively whic
