4 Apr
2011
4 Apr
'11
6:26 p.m.
Raison d'être being Paul's Unison and Reverb enhancements, jack session
support, panning tamed to a semi-sane standard, assorted bug fixes and
tweaking & tuning.
Special thanks go to Lars Luthman for conquering the heffalump bug,
whereby some ADnotes were incorrectly pitched on some 32 bit systems.
Thank you Lars. Thanks also go to the patient collaborators on
yoshimi-user. Thank you all!
There's a tarball and git, 0.060 branch _not_ master, at
<http://sourceforge.net/projects/yoshimi/files/>.
cheers, Cal
4 Apr
4 Apr
10:23 p.m.
:-(
Linking CXX executable yoshimi
CMakeFiles/yoshimi.dir/Misc/SynthEngine.cpp.o: In function
`SynthEngine::MasterAudio(float*, float*)':
SynthEngine.cpp:(.text+0x1483): undefined reference to `__sync_add_and_fetch_4'
CMakeFiles/yoshimi.dir/Misc/SynthEngine.cpp.o: In function
`SynthEngine::NoteOn(unsigned char, unsigned char, unsigned char)':
SynthEngine.cpp:(.text+0x2eaa): undefined reference to `__sync_add_and_fetch_4'
CMakeFiles/yoshimi.dir/Misc/Part.cpp.o: In function `Part::ComputePartSmps()':
Part.cpp:(.text+0x111f): undefined reference to `__sync_add_and_fetch_4'
collect2: ld returned 1 exit status
make[2]: *** [yoshimi] Error 1
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
make: *** [all] Error 2
yoshimi-0.058.1 compiled fine on the same host. How can I investigate
further?
Details: Linux From Scratch, kernel 2.6.38.2, gcc 4.4.1, ftlk-1.1.10 .
Regards, and thanks for your work,
Jeremy Henty
11:14 p.m.
On 4 April 2011 21:23, Jeremy Henty <onepoint(a)starurchin.org> wrote:
:-(
Linking CXX executable yoshimi
CMakeFiles/yoshimi.dir/Misc/SynthEngine.cpp.o: In function
`SynthEngine::MasterAudio(float*, float*)':
SynthEngine.cpp:(.text+0x1483): undefined reference to `__sync_add_and_fetch_4'
CMakeFiles/yoshimi.dir/Misc/SynthEngine.cpp.o: In function
`SynthEngine::NoteOn(unsigned char, unsigned char, unsigned char)':
SynthEngine.cpp:(.text+0x2eaa): undefined reference to `__sync_add_and_fetch_4'
CMakeFiles/yoshimi.dir/Misc/Part.cpp.o: In function `Part::ComputePartSmps()':
Part.cpp:(.text+0x111f): undefined reference to `__sync_add_and_fetch_4'
collect2: ld returned 1 exit status
make[2]: *** [yoshimi] Error 1
make[1]: *** [CMakeFiles/yoshimi.dir/all] Error 2
make: *** [all] Error 2
yoshimi-0.058.1 compiled fine on the same host. How can I investigate
further?
an allegedly monopolistic search engine returns:
http://stackoverflow.com/questions/130740/link-error-when-compiling-gcc-ato…
that and running ccmake and inspecting what I see there makes me think
you don't have core2/amd64 based system?
so try adding -march=i486 to the BuildOptionsBasic field when running ccmake.
my best guess.
James.
Details: Linux From Scratch, kernel 2.6.38.2, gcc 4.4.1, ftlk-1.1.10 .
Regards, and thanks for your work,
Jeremy Henty
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5 Apr
5 Apr
12:32 a.m.
James Morris wrote:
you don't have core2/amd64 based system?
It is an Athlon-64 system but Linux From Scratch builds everything in
32-bit mode:
$ uname -imp
i686 athlon-4 i386
so try adding -march=i486 to the
BuildOptionsBasic field when
running ccmake.
I like to script all my builds (it saves time remembering what on
earth I did 6 months later) so I added
-DCMAKE_C_FLAGS:STRING=-march=athlon-4 \
-DCMAKE_CXX_FLAGS:STRING=-march=athlon-4 \
to the cmake line - and it worked! (I don't know if I need both
flags, I may experiment more later.)
Thanks for your awesomely swift advice,
Jeremy Henty
6:39 a.m.
On 4 April 2011 23:32, Jeremy Henty <onepoint(a)starurchin.org> wrote:
I like to script all my builds (it saves time
remembering what on
earth I did 6 months later) so I added
-DCMAKE_C_FLAGS:STRING=-march=athlon-4 \
-DCMAKE_CXX_FLAGS:STRING=-march=athlon-4 \
to the cmake line - and it worked! (I don't know if I need both
flags, I may experiment more later.)
This seems slightly peculiar to me. I would have thought what with
running LFS, you specify all the compiler flags near the start of the
system build? Or is/does/should cmake not pick(ing) up variables from
the environment? Otherwise you'll end up having to do the same for
many applications.
(from very limited experience with DIY Linux and Gentoo).
James.
8:43 a.m.
James Morris wrote:
On 4 April 2011 23:32, Jeremy Henty
<onepoint(a)starurchin.org> wrote:
This is the first time I have needed to set -march, despite having
compiled (literally) hundreds of applications from source. There's
clearly something specific to yoshimi that is triggering this, though
it is possible that there is something very subtly broken with my gcc
that only this build has shown up. Incidentally, I compared the
CMakeCacheList.txt of the two builds and they were very different. It
looks as though more has changed under the hood than I imagined.
Thanks again,
Jeremy Henty
I like to script all my builds (it saves time
remembering what on
earth I did 6 months later) so I added
-DCMAKE_C_FLAGS:STRING=-march=athlon-4 \
-DCMAKE_CXX_FLAGS:STRING=-march=athlon-4 \
to the cmake line - and it worked! (I don't know if I need both
flags, I may experiment more later.)
This seems slightly peculiar to me. I would have thought what with
running LFS, you specify all the compiler flags near the start of
the system build? Or is/does/should cmake not pick(ing) up variables
from the environment? Otherwise you'll end up having to do the same
for many applications. 
9:19 a.m.
Quoting Jeremy Henty <onepoint(a)starurchin.org>rg>:
James Morris wrote:
> On 4 April 2011 23:32, Jeremy Henty <onepoint(a)starurchin.org> wrote:
>
> > I like to script all my builds (it saves time remembering what on
> > earth I did 6 months later) so I added
> >
> > -DCMAKE_C_FLAGS:STRING=-march=athlon-4 \
> > -DCMAKE_CXX_FLAGS:STRING=-march=athlon-4 \
> >
> > to the cmake line - and it worked! (I don't know if I need both
This is the first time I have needed to set -march,
despite having
compiled (literally) hundreds of applications from source. There's
clearly something specific to yoshimi that is triggering this,
Yoshimis CPU-feature detection more or less sucks :)
I managed to compile a couple of versions that segfaulted upon start
before I realized that ccmake thought my Athlon-XP 2000+ had the SSE2
instruction set.
9:46 a.m.
On 04/05/2011 09:19 AM, Peder Hedlund wrote:
Yoshimis CPU-feature detection more or less sucks :)
Yoshimi uses three pre-configured settings:
set (BuildOptions_x86_64AMD
"-O3 -march=athlon64 -m64 -Wall -ffast-math -fno-finite-math-only
-fomit-frame-pointer"
CACHE STRING "X86_64 compiler options"
)
set (BuildOptions_X86_64Core2
"-O3 -march=core2 -m64 -Wall -ffast-math -fno-finite-math-only
-fomit-frame-pointer"
CACHE STRING "X86_64 compiler options"
)
set (BuildOptionsBasic
"-O3 -msse -msse2 -mfpmath=sse -ffast-math -fomit-frame-pointer"
CACHE STRING "basic X86 complier options"
You can select those with ccmake and modify them if necessary. By
default Yoshimi uses the BuildOptionsBasic line.
Best,
Jeremy
4982
days inactive
4983
days old
linux-audio-user@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
cal -
James Morris -
Jeremy Henty -
Jeremy Jongepier -
Peder Hedlund