i guess they link libfftw statically AND dynamically
2006-08-04 21608, 2006
deadchip
at least that's how it looks like
2006-08-04 21612, 2006
luks
i've never seen this before
2006-08-04 21616, 2006
deadchip
well they for sure do link it dynamically
2006-08-04 21630, 2006
deadchip
luks: well and i assure you before we get into discussions that i must be doing something odd that i don't :P
2006-08-04 21633, 2006
deadchip
(just a precaution :P)
2006-08-04 21654, 2006
deadchip
they link against -lfftw3
2006-08-04 21659, 2006
deadchip
tw3
2006-08-04 21601, 2006
deadchip
and then they have:
2006-08-04 21606, 2006
luks
yep, but why statically? :)
2006-08-04 21608, 2006
deadchip
well AFLIB
2006-08-04 21611, 2006
deadchip
luks: no idea
2006-08-04 21616, 2006
deadchip
cause they're closed source people
2006-08-04 21620, 2006
deadchip
they always develop like that
2006-08-04 21634, 2006
luks
it links dynamically to fttw3 on here
2006-08-04 21639, 2006
luks
-on
2006-08-04 21644, 2006
tru
I had that problem on macosx.
2006-08-04 21649, 2006
deadchip
luks:
2006-08-04 21653, 2006
deadchip
AFLIB/.libs/libaflib.a(align.o):align.c:(.text+0x0): first defined here
2006-08-04 21654, 2006
tru
I remcompiled fttw3 dynamic only.
2006-08-04 21603, 2006
deadchip
yeah that's what i was about to do
2006-08-04 21612, 2006
deadchip
but i first wanted to find out what the reason/bug is in their buildsystem
2006-08-04 21632, 2006
luks
well, i think it's a problem with your setup
2006-08-04 21636, 2006
deadchip
ahem
2006-08-04 21641, 2006
deadchip
look what tru just said
2006-08-04 21601, 2006
deadchip
it might be, "of course" a problem with both our setups >_>
2006-08-04 21604, 2006
deadchip
"sure" o_O
2006-08-04 21638, 2006
luks
no, i mean, do you want to link to fftw3 statically or dynamically?
2006-08-04 21643, 2006
deadchip
well i'm trying to find the reason and submit them a patch
2006-08-04 21649, 2006
deadchip
luks: it's not the point what _i_ want
2006-08-04 21654, 2006
deadchip
that thing should not try to link boht
2006-08-04 21656, 2006
deadchip
both*
2006-08-04 21603, 2006
luks
well, it uses -lfftw3
2006-08-04 21612, 2006
deadchip
yeah and somehow it also links to libfftw3.a
2006-08-04 21616, 2006
deadchip
it's obvious
2006-08-04 21620, 2006
deadchip
look at what i pasted above
2006-08-04 21645, 2006
deadchip
luks: really i'm coding and buildsystem (at least autotools) and gcc/g++ literate enough to tell you that this is what this thing is trying to do
2006-08-04 21646, 2006
luks
ah, i see
2006-08-04 21648, 2006
deadchip
and i'm trying to find out why
2006-08-04 21616, 2006
luks
well, this looks more like a libtool problem
2006-08-04 21618, 2006
deadchip
it could be, though, a libfftw3 bug
2006-08-04 21625, 2006
luks
it passes -lfftw3 to libtool
2006-08-04 21627, 2006
luks
and libtool uses /usr/lib/libfftw3.a
2006-08-04 21628, 2006
deadchip
but
2006-08-04 21639, 2006
deadchip
luks: that would be no problem
2006-08-04 21649, 2006
deadchip
if it wouldn't at the same time to link the solib as well
2006-08-04 21656, 2006
deadchip
(or .dylib on osx then)
2006-08-04 21620, 2006
deadchip
yeah i have it only built statically
2006-08-04 21631, 2006
deadchip
i actually thought up to now that libfftw3 exists in both forms
2006-08-04 21643, 2006
deadchip
so, the problem is, it doesn't know that it links it statically
2006-08-04 21653, 2006
deadchip
basically, sort of, you're right
2006-08-04 21657, 2006
deadchip
but they need to either:
2006-08-04 21604, 2006
luks
stupid question, but do you have installed the dynamic lib?
2006-08-04 21613, 2006
deadchip
- check for fftw3 being present as a dynamically linkable lib, and otherwise not build libofa
2006-08-04 21614, 2006
deadchip
or
2006-08-04 21636, 2006
deadchip
- adjust their buildsystem to link properly against libfftw3 as a static lib
2006-08-04 21642, 2006
deadchip
luks: no i haven't but that is not the point
2006-08-04 21647, 2006
deadchip
you see you're going to tell me
2006-08-04 21652, 2006
deadchip
<luks> well, that is the problme
2006-08-04 21653, 2006
deadchip
em*
2006-08-04 21655, 2006
deadchip
but it's not
2006-08-04 21609, 2006
deadchip
well in the _end_, right now, it is the problem
2006-08-04 21613, 2006
luks
ideally it should link to static version as well, but obviously it doesn't
2006-08-04 21616, 2006
deadchip
but the general problem is that their build system is erroneus
2006-08-04 21619, 2006
luks
but i don't think that's libofa bug
2006-08-04 21619, 2006
deadchip
yeah
2006-08-04 21624, 2006
deadchip
sure it is
2006-08-04 21627, 2006
luks
how?
2006-08-04 21642, 2006
deadchip
-lblah doesn't specify whether it should be a dynamically linkable lib or a static lib
2006-08-04 21601, 2006
deadchip
their build system needs to check for the presence of the dynamic libfftw3
2006-08-04 21603, 2006
luks
what if i have a static fftw3 (that actually works) and want to it?
2006-08-04 21605, 2006
deadchip
they can do that very easily with
2006-08-04 21607, 2006
deadchip
AC_CHECK_LIB()
2006-08-04 21610, 2006
deadchip
i think
2006-08-04 21616, 2006
deadchip
since nm -D will not work with a static lib
2006-08-04 21618, 2006
deadchip tries
2006-08-04 21620, 2006
srotta
Hmm. A quick question: shouldn't singles be (generally) named after their main track?
2006-08-04 21644, 2006
deadchip
let's see
2006-08-04 21606, 2006
luks
so you are saying that the build system should disallow linking to static version, right?
2006-08-04 21607, 2006
deadchip
hmmm ok AC_CHECK_LIB does not use nm or anything
2006-08-04 21610, 2006
deadchip
as the check passes
2006-08-04 21626, 2006
deadchip
luks: either that, or it should accomodate for linking against the static version
2006-08-04 21628, 2006
mudcrow
srotta: yes, usually
2006-08-04 21629, 2006
srotta
I'm seeing quite many singles that have both A and B side in the release title.
2006-08-04 21636, 2006
deadchip
right now, it is unaware that the lib might be present as a static lib
2006-08-04 21617, 2006
luks
but what if i *want* link to the static version?
2006-08-04 21629, 2006
deadchip
then you have to specify --with-fftw3-static to libofa's configure
2006-08-04 21637, 2006
deadchip
which currently does not exist but they must add it
2006-08-04 21653, 2006
luks is not sure if that's a good idea
2006-08-04 21618, 2006
deadchip is quite sure that while it might be not neccessarily a "good idea", it's the only correct technical solution
2006-08-04 21639, 2006
deadchip
look i don't code since 3 days ago ok? :P
2006-08-04 21628, 2006
luks
well, if you have installed both versions libtool will prefer the dynamic one. if you have only the dynamic one, libtool will use it. if you have *correct* static lib, libtool will use it
2006-08-04 21634, 2006
luks
where's the problem?
2006-08-04 21643, 2006
luks
the only problem is if you have broken static version
2006-08-04 21643, 2006
deadchip
i pasted you the problem
2006-08-04 21654, 2006
deadchip
i don't understand why you don't see that libofa is just broken atm
2006-08-04 21655, 2006
deadchip
?
2006-08-04 21659, 2006
luks
can you link anything agains that static lib?
2006-08-04 21600, 2006
deadchip
what is the problem in seeing that?
2006-08-04 21611, 2006
deadchip
are you basically saying that i _must_ have the dynamic lib installed in order to build libofa
2006-08-04 21616, 2006
deadchip
and if i _don't_ have it
2006-08-04 21628, 2006
deadchip
?
2006-08-04 21630, 2006
luks
but what i _want_ to use the static lib
2006-08-04 21631, 2006
srotta
mudcrow: I also find it annoying, that for some reason there are several vinyl singles that are categorized as EP's :P
2006-08-04 21631, 2006
deadchip
is that your statement?
2006-08-04 21632, 2006
luks
?
2006-08-04 21633, 2006
deadchip
luks: ^
2006-08-04 21640, 2006
deadchip
luks: ^
2006-08-04 21606, 2006
luks
you get the error because your libfftw3 install it broken
2006-08-04 21610, 2006
deadchip
there are a few other apps that i know of that allow of linking to another lib dynamically or statically and they are _aware_ of the fact that this other lib can come in both forms
2006-08-04 21619, 2006
deadchip
and they all have a switch lib --with-somelib-static
2006-08-04 21630, 2006
deadchip
and they do prefer the dynamic version usually, some do it the other way round
2006-08-04 21631, 2006
mudcrow
srotta: a lot of singles are a mess, listed as all sorts of things.
2006-08-04 21640, 2006
deadchip
but this is nothing unusual, and not weird and a "bad idea" in any way
2006-08-04 21644, 2006
deadchip
luks: lol?
2006-08-04 21648, 2006
deadchip
luks: how is it broken?
2006-08-04 21658, 2006
deadchip
i simply did not specify to build the dynamic lib
2006-08-04 21659, 2006
luks
can you link *anything* to that fftw3?
2006-08-04 21602, 2006
deadchip
that does not qualify as broken
2006-08-04 21618, 2006
deadchip
luks: even if i can't it does not qualify as broken if it's an option to build fftw3 like that
2006-08-04 21603, 2006
luks
why should it require you to use the dynamic link?
2006-08-04 21617, 2006
luks
*lin
2006-08-04 21619, 2006
luks
bleh!
2006-08-04 21624, 2006
luks
dynamic lib
2006-08-04 21647, 2006
deadchip
luks:
2006-08-04 21649, 2006
deadchip
[mderezynski [at core] ~]$
2006-08-04 21654, 2006
deadchip
sure i can link something else against it
2006-08-04 21606, 2006
deadchip
as i'm telling you THEIR (libofa's) setup is broken
2006-08-04 21613, 2006
deadchip
not mine, not libfftw3, or anything else
2006-08-04 21629, 2006
Freso
Whee! Almost done with the composers on Rubai! :D
2006-08-04 21650, 2006
luks
deadchip: you don't use any fftw3 code there
2006-08-04 21658, 2006
deadchip
luks: that doesn't matter
2006-08-04 21604, 2006
deadchip
luks: if you are familiar with linking
2006-08-04 21610, 2006
deadchip
luks: then you should know that this doesn't matter
