Ticket #532 (closed wishlist: fixed)

Opened 4 years ago

Last modified 10 months ago

qlib2 and m32

Reported by: stefan Owned by: somebody
Priority: minor Milestone: Linux
Component: ALL modules Version:
Keywords: Cc:


removing m32 in the ew_unix.bash environment file for raspberry pi compilation doesn't remove m32 from libsrc/qlib2/Makefile it would be nice if this was made into an environment variable so it did

Change History

comment:1 Changed 10 months ago by baker


Can you confirm that this is still a problem? If it is still a problem, can you give some more information about the compiler? gcc? version? There are 64-bit ARM processors now. Is it that -m32/-m64 are x86-specific flags?

comment:2 Changed 10 months ago by stefan

I no longer have access to that pi hardware, so I can't retest today. I'll update the ticket if I obtain access again.

comment:3 Changed 10 months ago by baker

  • Status changed from new to closed
  • Resolution set to fixed

When I updated qlib2 to the latest version 1.55 (2018.137), I modified src/libsrc/makefile.unix to override the macro definitions for CC and CFLAGS in the qlib2 Makefile to use those provided by the Earthworm environment script.

To fix this problem, all I had to do was add C32="" (C64="") to the qlib2 make command. For example, for EWBITS=32:

qlib232:: FRC
	@echo ------; cd qlib2; echo Making $@ in:; pwd; \
		make CC="$(CC)" CFLAGS_SITE="$(CFLAGS)" C32="" all32; \
		mkdir -p lib_ew; cp lib/*.a lib_ew

Defining C32="" this way overrides the definition of C32=-m32 in the qlib2 Makefile.

However EWBITS gets defined in CFLAGS (GLOBALFLAGS) in ew_linux.bash—including nothing—is what will get used when qlib2 is compiled.

Fixed in r7463.

Note: See TracTickets for help on using tickets.