Esddsp returns bus error.
Felipe Mendes
man.of.golden.words at gmail.com
Tue Mar 13 06:10:25 UTC 2007
Hello! I just started using FreeBSD and I have been finding some problems
with the stable release...
After building the world and porting all my preferred app's I can't figure
out how to compile the Enlightened Sound Daemon.
No matter what I do, everytime I run esddsp, during the compilation these
warnings always appear, I think that's why I receive a "Bus Error: Core
Dumped" when trying to run esddsp ...:
/usr/local/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
-I. -I/usr/local/include -DSYSCONFDIR=\"/usr/local/etc\"
-DSERVERDIR=\"/usr/local/bin\" -g -O2 -I/usr/local/include -Wall -MT
esddsp.lo -MD -MP -MF .deps/esddsp.Tpo -c -o esddsp.lo esddsp.c
gcc -DHAVE_CONFIG_H -I. -I/usr/local/include
-DSYSCONFDIR=\"/usr/local/etc\" -DSERVERDIR=\"/usr/local/bin\" -g -O2
-I/usr/local/include -Wall -MT esddsp.lo -MD -MP -MF .deps/esddsp.Tpo -c
esddsp.c -fPIC -DPIC -o .libs/esddsp.o
esddsp.c: In function `open_wrapper':
esddsp.c:228: warning: `mode_t' is promoted to `int' when passed through
`...'
esddsp.c:228: warning: (so you should pass `int' not `mode_t' to `va_arg')
esddsp.c:228: note: if this code is reached, the program will abort
esddsp.c: In function `open':
esddsp.c:276: warning: `mode_t' is promoted to `int' when passed through
`...'
esddsp.c:276: note: if this code is reached, the program will abort
esddsp.c: In function `open64':
esddsp.c:303: warning: `mode_t' is promoted to `int' when passed through
`...'
esddsp.c:303: note: if this code is reached, the program will abort
esddsp.c: In function `fopen_wrapper':
esddsp.c:343: warning: control reaches end of non-void function
I tried changing CFLAGS to "-O -g -pipe" but it didn't worked. Neither a
portupgrade -a. I am almost sure it's not a problem with esound but with
some other app, because I tried to download the .tbz binary and the problem
persists...
I did a make check under libaudiofile dir and all tests passed.
Tried to recompile some app's (glib's, for instance) with some "safe"
CFLAGS but it still persists...
So, Here I am. :-D
Any clues? Need more info?
Your help is appreciated, thanks.
--
Felipe Mendes - 16 years
More information about the freebsd-ports
mailing list