So xmame compiles now but seems to be too big to load on macppc. This is the
output:
$ xmame
ksh: xmame: Cannot allocate memory
$ l /usr/local/bin/xmame
-r-xr-xr-x 1 root bin 42785500 Aug 16 12:43 /usr/local/bin/xmame
Any clues?
On Mon, Aug 14, 2006 at 11:06:15PM +0200, Matthias Kilian
On Monday 14 August 2006 5:06 pm, Matthias Kilian wrote:
Linking xmame.x11 ...
[...]
/usr/lib/crt0.o(.text+0x58): In function `_start':
: relocation truncated to fit: R_PPC_REL24 exit
/usr/lib/crtbegin.o(.text+0x134): In function `__register_frame_info':
: relocation truncated to fit:
# make install
=== Faking installation for xmame+xmess-0.104-x11
gmake[1]: Entering directory
`/usr/ports/emulators/xmame/w-xmame+xmess-0.104-x11/xmame-0.104'
Installing binaries under
/usr/ports/emulators/xmame/w-xmame+xmess-0.104-x11/fake-macppc-x11/usr/local/bin...
install -d -o root -g bin
* Marco Peereboom [2006-08-14]:
I did an install on i386 and that worked. Any clues?
Not without a full build log.
Nikolay
--
It's all part of my Can't-Do approach to life. Wally
What's the preferred method to collect that?
Script? pipe?
On Mon, Aug 14, 2006 at 03:38:36PM +0200, Nikolay Sturm wrote:
* Marco Peereboom [2006-08-14]:
I did an install on i386 and that worked. Any clues?
Not without a full build log.
Nikolay
--
It's all part of my Can't-Do
Here it is.
On Mon, Aug 14, 2006 at 04:25:36PM +0200, Nikolay Sturm wrote:
* Marco Peereboom [2006-08-14]:
[full build log]
What's the preferred method to collect that?
make clean
make fake /tmp/xmame.log 21
Nikolay
xmame.log.gz
Description: application/gunzip
On Mon, Aug 14, 2006 at 03:54:59PM -0500, Marco Peereboom wrote:
Here it is.
And this is the real error:
Linking xmame.x11 ...
[...]
/usr/lib/crt0.o(.text+0x58): In function `_start':
: relocation truncated to fit: R_PPC_REL24 exit
/usr/lib/crtbegin.o(.text+0x134): In function
