Error when using -mips4

New Message Reply Date view Thread view Subject view Author view

ulf.yngwe++at++mandator.se
Fri, 2 May 1997 09:31:05 +0200


When i compile the following program with the -mips4 flag I get the error
shown below
when I run it. If I use the -mips2 flag it works fine. Does anyone know if
I should
use anymore flag to get it running or is it a bug. I use IRIX 6.3 and
Performer 2.1
on an O2.

#include <unistd.h>
#include <bstring.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <stdlib.h>

#include <stdio.h>
#include <string.h>
#include <malloc.h>
#include <getopt.h>
#include <sys/time.h>
#include <math.h>

#include <Performer/pf.h>
#include <Performer/pfutil.h>
#include <Performer/pfdu.h>

void main(
  )
{
    /* Initialize Performer */
    pfInit();

    pfConfig();

    sleep(20);
}
/* === */

#>make pffault
        /usr/bin/cc -mips4 -o pffault pffault.c -lpf_ogl -lpfdu_ogl
-lpfutil_ogl -limage -lGLU -lGL -lXext -lfpe -lm -lc
ld32: WARNING 84: /usr/lib32/libpfdu_ogl.so is not used for resolving any
symbol.
ld32: WARNING 85: definition of __checktraps in /usr/lib32/mips4/libfpe.so
preempts that definition in /usr/lib32/mips4/libc.so.
ld32: WARNING 85: definition of __readenv_sigfpe in
/usr/lib32/mips4/libfpe.so preempts that definition in
/usr/lib32/mips4/libc.so.
#>pffault
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 141 (GLX)
  Minor opcode of failed request: 5 (X_GLXMakeCurrent)
  Serial number of failed request: 0
  Current serial number in output stream: 21

=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:11 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.