[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> > gcc -static -DALLEGRO_STATICLINK -o demo demo.c `allegro-config
> > --static`
>
> /usr/local/lib/liballeg.a(umodules.o)(.text+0x1d9): In function
`_unix_load_modules':
> : warning: Using 'dlopen' in statically linked applications requires at
> : runtime the shared libraries from the glibc version used for linking
I don't get them on my system (binutils 2.14). Could you run 'ldd' on the
executable?
> For me, the resulting executable is huge, but still, it works. I guess I
> have that "shared libraries from the glibc version used for linking"
> installed - so that explains why it works. You probably don't have them,
> so it just aborts. (Just a guess.)
It crashes on my system with:
Core was generated by `./demo'.
Program terminated with signal 11, Segmentation fault.
#0 0x0809650c in _xwin_signal_handler ()
(gdb) bt
#0 0x0809650c in _xwin_signal_handler ()
#1 0x08096500 in stretch_sprite ()
#2 <signal handler called>
#3 0x0809650c in _xwin_signal_handler ()
#4 0x08096500 in stretch_sprite ()
#5 <signal handler called>
#6 0x0809650c in _xwin_signal_handler ()
#7 0x08096500 in stretch_sprite ()
#8 <signal handler called>
...
On the other hand, linking against Allegro-static but without -static works.
> I'm still puzzled why I could use -static in the past and even 2 days
> ago, and now get these warnings. I even remember sending a -static
> executable to someone once, to test binary compatibility of Allegro in
> linux, and it worked. Maybe someone else here can shed some light on the
> issue.
Pretty weird indeed.
--
Eric Botcazou