I maintain the the rpm package for fedora. I'm having trouble getting usable debuginfo from the rpmbuild. Attempting to solve this I notice that our build system required flags are being ignored or overwritten during the build -
`CXXFFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector -param=ssp-buffer-size=4 -m64
-mtune=generic'`
, then make, log shows eg:
`g++ -O2 -Wall -msse2 -fno-rtti -pipe -ffunction-sections
-fomit-frame-pointer -Wno-format-y2k -fPIC -fno-exceptions -fno-strict-aliasing -I/usr/include/freetype2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT -o rakarrack main.o jack.o rakarrack.o process.o fileio.o varios.o Reverb.o Chorus.o EffectLFO.o Echo.o Phaser.o Distorsion.o EQ.o Compressor.o AnalogFilter.o Alienwah.o Filter.o DynamicFilter.o SVFilter.o FormantFilter.o FilterParams.o Pan.o Harmonizer.o smbPitchShift.o Tuner.o MusicDelay.o Gate.o RecognizeNote.o RecChord.o rkrMIDI.o MIDIConverter.o -lfltk_images -lpng -lz -ljpeg -lfltk -lasound -ljack -lpthread -lrt -lXpm`
It seems that while configure suggests that the environment will be used, something is going wrong.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Joseph, I created a patch of configure.in.1.14 against the one in 0.3.0, and this successfully passes our build system CXXFLAGS into the compile stages, and also generates good -debuginfo packages.
For others, note the additional BR requirement of fftw-devel .
Also, once built I found that the fedora flags invoke the buffer overflow checks, and they capture a buffer overflow in RecChord.h/.c:
thread apply bt showed error at line 404 of .c
case 5:
strcpy (Chord5.Nom, ChN_.Nom);
It seems width of .Nom=11, while ChN.Nom can be 16, and/or some of those chord text names must be wider than 11 bytes.
It might make sense to use constants for the differing widths ?
Anyway, basic patch, probably better ways to resolve it:
_
diff -ur rakarrack-0.3.0.orig/src/RecChord.h rakarrack-0.3.0/src/RecChord.h--- rakarrack-0.3.0.orig/src/RecChord.h 2008-11-06 00:45:14.000000000 +1100+++ rakarrack-0.3.0/src/RecChord.h 2010-01-08 00:41:01.000000000 +1100@@ -101,7 +101,7 @@
int di2;
int di3;
int di4;
- char Nom[10];+ char Nom[16];
} Chord5[67];
int Ch[34][13];
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks .. for your help, I will change this line right now, I'm only a entusiast amateur programmer, and seeing that now I know that I use jurassic methods to debug the program.
Please can you send me the configure.in and some info of how can I do things like that? or just a url where to find the info.
Please send to my personal email holborn@telefonica.net
Thanks again.
Josep
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I maintain the the rpm package for fedora. I'm having trouble getting usable debuginfo from the rpmbuild. Attempting to solve this I notice that our build system required flags are being ignored or overwritten during the build -
`CXXFFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector -param=ssp-buffer-size=4 -m64
-mtune=generic'`
, then make, log shows eg:
`g++ -O2 -Wall -msse2 -fno-rtti -pipe -ffunction-sections
-fomit-frame-pointer -Wno-format-y2k -fPIC -fno-exceptions -fno-strict-aliasing -I/usr/include/freetype2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT -o rakarrack main.o jack.o rakarrack.o process.o fileio.o varios.o Reverb.o Chorus.o EffectLFO.o Echo.o Phaser.o Distorsion.o EQ.o Compressor.o AnalogFilter.o Alienwah.o Filter.o DynamicFilter.o SVFilter.o FormantFilter.o FilterParams.o Pan.o Harmonizer.o smbPitchShift.o Tuner.o MusicDelay.o Gate.o RecognizeNote.o RecChord.o rkrMIDI.o MIDIConverter.o -lfltk_images -lpng -lz -ljpeg -lfltk -lasound -ljack -lpthread -lrt -lXpm`
It seems that while configure suggests that the environment will be used, something is going wrong.
I will check that thanks.
Josep
Oops, forgot to mention that I'm working with 0.3.0 currently. Is the next release just around the corner ?
Yes … hope we will release at the end of this month
Please can you check if the configure.in located in the CVS tree is enough? I'm not a Auto Tools guru and maybe I need some help :-)
Hi Joseph, I created a patch of configure.in.1.14 against the one in 0.3.0, and this successfully passes our build system CXXFLAGS into the compile stages, and also generates good -debuginfo packages.
For others, note the additional BR requirement of fftw-devel .
Also, once built I found that the fedora flags invoke the buffer overflow checks, and they capture a buffer overflow in RecChord.h/.c:
thread apply bt showed error at line 404 of .c
case 5:
strcpy (Chord5.Nom, ChN_.Nom);
It seems width of .Nom=11, while ChN.Nom can be 16, and/or some of those chord text names must be wider than 11 bytes.
It might make sense to use constants for the differing widths ?
Anyway, basic patch, probably better ways to resolve it:
_
Hi
Thanks .. for your help, I will change this line right now, I'm only a entusiast amateur programmer, and seeing that now I know that I use jurassic methods to debug the program.
Please can you send me the configure.in and some info of how can I do things like that? or just a url where to find the info.
Please send to my personal email holborn@telefonica.net
Thanks again.
Josep