[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Exec format error, but no gcc warnings



On Mon, Jan 08, 2001 at 03:07:38PM -0500, Jonathan D. Proulx wrote:
> On Mon, Jan 08, 2001 at 12:32:18PM -0500, Ben Collins wrote:
> :On Mon, Jan 08, 2001 at 11:37:09AM -0500, Jonathan D. Proulx wrote:
> :> 
> :> It then builds with with the same results from "ldd" and "file", BTW
> :> using g77 as above, this builds fine on x86 arch, don't know wether
> :> that's relevent at all...
> :> 
> :
> :Hmm...no experience with g77, but it looks like it is compiling for the
> :wrong arch. What version of g77 is this? Can you provide me a sample g77
> :"hello world" compiled this way, and tell me if it works?
> 
> OK, I don't do Fortran either, so I ditched g77 as it's not required,
> made clean removed the broken binaries (which make clean doesn't).
> 
> What I've got in the make file now:
> 
> CC           = gcc
> CCFLAGS      = -fomit-frame-pointer -O3 -funroll-loops
> LINKER       = ld
> LINKFLAGS    = $(CCFLAGS) -lm -lmpi -lcblas
> 
> (I've previously added -Wall to CCFLAGS and gotten no warnings)
> 
> using ld I do get one warning:
> ld: warning: cannot find entry symbol _start; defaulting to 00000000000124ac

Using gcc for linking should be fine. Sounds to me like you have some
odd flags coming from somewhere or some asm with V9 specifics (you don't
get a SPARCPLUS V8+ binary using -mv8plus, it's what you see when you
compile with -mv9). So, I am assuming that you might be getting a
sparc64 compilation environment (did you say you were compiling on an
ultrasparc?).

Try compiling with the sparc32 command ("sparc32 make all"), which
should fake the build into thinking sparc-linux, instead of
sparc64-linux.

-- 
 -----------=======-=-======-=========-----------=====------------=-=------
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'



Reply to: