Could you check if following variables are set?

env XLIB_SKIP_ARGB_VISUALS=1 G_SLICE="always-malloc"

(In reply to comment #1)
> Could you check if following variables are set?
> 
> env XLIB_SKIP_ARGB_VISUALS=1 G_SLICE="always-malloc"
> 

No.They were not.
I set them so when I do env to display my env,now they are set:
...
XLIB_SKIP_ARGB_VISUALS=1
G_SLICE=always-malloc
...

But,the problem is the same and bash displays exactly the same error message
I reported previously.My xorg.conf file is set for 16 bit color(it seems
that my graphic card under Linux does not support more),could that be
the problem?Is there a way to surpass this?

(In reply to comment #2)
> (In reply to comment #1)
> > Could you check if following variables are set?
> > 
> > env XLIB_SKIP_ARGB_VISUALS=1 G_SLICE="always-malloc"
> > 
> 
> No.They were not.
> I set them so when I do env to display my env,now they are set:
> ...
> XLIB_SKIP_ARGB_VISUALS=1
> G_SLICE=always-malloc
> ...
> 
> But,the problem is the same and bash displays exactly the same error message
> I reported previously.My xorg.conf file is set for 16 bit color(it seems
> that my graphic card under Linux does not support more),could that be
> the problem?Is there a way to surpass this?
> 

Perhaps the crash is not linked with that assertion.
I suspect more a problem with GL libs used by default.
Our distributions include static Mesa libs because several Linux libraries are buggy.
Could you test an Amaya distribution?

Amaya-11.1 distribution does not have pre-compiled binaries for the LinuxPPC
architecture,so,I cannot use one of them.I will try to compile from source
using the libraries that come with amaya sources,and not with system libraries.
I tried once and I could not compile,in the make (build stage) accused error.
I will try again.

What are the options I need to pass to configure to build the amaya binary
with static mesa?

P.S. I installed amaya-10.1 from debian unstable with all necessary libraries
using the debian package management system,and surprise!!! I got exactly the
same warnings I reported with amaya-11.1.

When I try to compile amaya-11.1 without using the options --enable-system-wx
--enable-system-libwww --enable-system-raptor,and using the libraries that
come with amaya sources,I get errors.

the final lines of these errors:

tnl/t_vertex_sse.c:653:error: file_XMM undeclared(first use in this function)
tnl/t_vertex_sse.c:656:warning:implicit declaration of function x86_init_func_
size
tnl/t_vertex_sse.c:659:warning:implicit declaration of function x86_release_func
make[4]:*** [tnl/t_vertex_sse.o] Error 1

So,it seems difficult without changes to the source code to compile on the
PowerPC platform with the libraries that come with amaya sources.
Using system libraries compiles easily but the problem arises at run time,
when whe try to run the binary.

(In reply to comment #5)
> When I try to compile amaya-11.1 without using the options --enable-system-wx
> --enable-system-libwww --enable-system-raptor,and using the libraries that
> come with amaya sources,I get errors.
> 
> the final lines of these errors:
> 
> tnl/t_vertex_sse.c:653:error: file_XMM undeclared(first use in this function)
> tnl/t_vertex_sse.c:656:warning:implicit declaration of function x86_init_func_
> size
> tnl/t_vertex_sse.c:659:warning:implicit declaration of function
> x86_release_func
> make[4]:*** [tnl/t_vertex_sse.o] Error 1
> 
> So,it seems difficult without changes to the source code to compile on the
> PowerPC platform with the libraries that come with amaya sources.
> Using system libraries compiles easily but the problem arises at run time,
> when whe try to run the binary.
> 

I never try to compile Amaya on that platform, but I suggest you keep the  --enable-system-raptor option and try to compile with other local libraries.
For Mesa, I guess you have to select the linux-ppc-static configuration as current. For that, after the untar, 
"cp Mesa/configs/linux-ppc-static Mesa/configs/current"

(In reply to comment #5)
> When I try to compile amaya-11.1 without using the options --enable-system-wx
> --enable-system-libwww --enable-system-raptor,and using the libraries that
> come with amaya sources,I get errors.
> 
> the final lines of these errors:
> 
> tnl/t_vertex_sse.c:653:error: file_XMM undeclared(first use in this function)
> tnl/t_vertex_sse.c:656:warning:implicit declaration of function x86_init_func_
> size
> tnl/t_vertex_sse.c:659:warning:implicit declaration of function
> x86_release_func
> make[4]:*** [tnl/t_vertex_sse.o] Error 1
> 
> So,it seems difficult without changes to the source code to compile on the
> PowerPC platform with the libraries that come with amaya sources.
> Using system libraries compiles easily but the problem arises at run time,
> when whe try to run the binary.
> 

I generated for you a snapshot with a wxWidgets patch that skips the "gtk_widget_set_colormap" call according to new gtk2 versions.
see http://wam.inrialpes.fr/software/amaya/amaya-fullsrc-11.2-pre1.tgz

I used the patched sources indicated with the previous comment,and only used the
option --enable-system-raptor,I also used linux-ppc-static as current.
The compilation was OK and the resulting amaya binary performs OK so far,
anyway I only tested opening menus,opening dialogs,and moving around the amaya
GUI interface.I did not produce any real work,webpages etc.,yet.So far it
seems fine,and this specific problem seems solved.

Only as curiosity I also compiled with the patched sources using my previously
used options:

../configure --prefix=/usr/local/amaya --enable-system-wx --enable-system-libwww --enable-system-raptor

and even with the patched sources the resulting binary gives exactly the same
warnings I reported,and crashes after 1 or 2 seconds after displaying the main
window.Anyway,now I know the right method to get amaya compiling and working 
fine. 


                        Thanks,for the effective support.