#musicbrainz

/

      • ruaok
        fedex hasn't updated the tracking info for it. bastards.
      • warp
        ruaok: i need new wxpython don't I? i have a 2.6.0.0 laying about from a previous picard install.
      • ruaok
        good enough for govt work.
      • yalaforge
      • the XML is malformed, I think there's a <release-info-list> </release-event-list> or something
      • g0llum
        To All: here's a mod which is interesting from a CodeOfConduct POV. give your opinions, if you have time http://musicbrainz.org/showmod.html?modid=4223575
      • ruaok
        yalaforge: yes. remind me,... release-even-list is correct, right>
      • yalaforge
        release-event-list, yup
      • perfect name, I like it :-)
      • ruaok
        ok, fixed.
      • yalaforge
        thanks
      • yay, works
      • ruaok
        g0llum: yes, that bugs.
      • and chocomo won't change his tune.
      • keeps doing it.
      • I think nikki_'s suggestion of the first no vote needs a comment makes sense to me.
      • ok, enough for me tonight.
      • I;m off a little early todayl.
      • yalaforge
        a little early :-)
      • schlaf' gut!
      • ruaok
        ya, only 12:40 this time.
      • warp starts on the first ./configure
      • normally I leave at 2:30 at the latest.
      • warp
        goodnight ruaok :)
      • ruaok
        but I have two servers running in my office and I am wearing ear-plugs.
      • not a good environment. sleep is better. :-)
      • thanks and good night!
      • ruaok has quit
      • orogor joined the channel
      • warp
        checking for mb_GetVersion in -lmusicbrainz... no
      • :(
      • yalaforge
        is it installed. and if yes, via package or from source?
      • warp
        source.
      • -L/home/warp/opt/picard/lib -lmusicbrainz
      • luks
        it doesn't use pkg-config, afaik
      • set the LD_LIBRARY_PATH
      • warp
        libmusicbrainz does, so everything using it should do too IMO :)
      • luks: LD_LIBRARY_PATH is set too.
      • luks
        hm
      • yalaforge
        yup. I added the pkg-config for libmb, but nobody wanted to use it :-/
      • this has nothing to do with the LD_LIBRARY_PATH
      • luks
        actually, it has :)
      • yalaforge
        LD_LIBRARY_PATH is for the dynamic linker
      • warp
        LD_LIBRARY_PATH is only runtime, not build time.
      • yalaforge
        the problem is probably the build time one, yup
      • luks
        i had the same issues, and LI_LIBRARY_PATH solved it
      • that'
      • warp
        yalaforge: well, thanks for adding the pkg-config stuff,.. usually it helps prevent this sort of trouble.
      • luks
        s because configure needs to compile and link a test program
      • warp
        :)
      • yalaforge
        luks: if 'ld' or 'gcc' doesn't find the library, it doesn't help
      • warp: check your config.log
      • warp
        configure:21351: g++ -o conftest -g -O2 -Wall -O2 conftest.cc -lmusicbrainz -lz >&5
      • /usr/bin/ld: cannot find -lmusicbrainz
      • yalaforge
        LD_FLAGS='-L/home/warp/opt/picard/lib' ./configure
      • yalaforge hopes configure passes the linker flags on :-)
      • LD_FLAGS='-L/home/warp/opt/picard/lib -Wl,-R,/home/warp/opt/picard/lib' ./configure
      • this hardcodes the path for the dynamic linker. then LD_LIBRARY_PATH or /etc/ld.so.conf aren't needed
      • warp
        wow, now you're getting complicated :)
      • yalaforge has been through this crap a hundred times on NetBSD :-/
      • still not.
      • yalaforge
        config.log?
      • (this is libtp, right?)
      • warp
        still the same.
      • yes, it is libtunepimp.
      • warp has a look around configure.in
      • yalaforge
        ok, I'll have a look at it
      • yalaforge checks how the linker flags are passed around
      • warp
        it has stuff such as 'CFLAGS="$CFLAGS -Wall -O2"', but no mention of LFLAGS
      • yalaforge
        LD_FLAGS
      • warp
        erm, LD_FLAGS
      • warp [at ararita]:~/usr/src/picard/libtunepimp-0.4.2$ cat configure configure.in | grep LD_FLAGS | wc
      • 0 0 0
      • :)
      • yalaforge
        LIBS is overwritten, it seems
      • luks
        well, `LD_LIBRARY_PATH=/home/luks/picard/lib ./configure --prefix=/home/luks/picard` solved all the problems for me here on ubuntu
      • yalaforge
        it shouldn't work :-)
      • luks
        well, it does ;)
      • yalaforge
        warp: try LIBS instead of LD_FLAGS
      • luks_ joined the channel
      • warp
        hm, odd
      • checking for version >= 2.1.0 in -lmusicbrainz... no
      • yalaforge
        using LIBS?
      • warp
        yes
      • configure:21433: g++ -o conftest -g -O2 -Wall -O2 conftest.cc -lmusicbrainz >&5
      • conftest.cc:33:30: error: musicbrainz/mb_c.h: No such file or directory
      • conftest.cc: In function 'int main()':
      • yalaforge
        ahhh :-)
      • warp
        and i actually already included CFLAGS too.
      • yalaforge
        oh.
      • warp
        LIBS=`pkg-config --libs libmusicbrainz` CFLAGS=`pkg-config --cflags libmusicbrainz` ./configure --prefix=/home/warp/opt/picard
      • yalaforge
        use CXXFLAGS
      • warp
        doh, ofcourse.
      • yalaforge
        libtp's configure is completely broken.
      • warp agrees :)
      • the LIBS trick only works on *some* architectures
      • well, installing libs in a non-standard place is still your fault :-)
      • warp
        if you would seriously object to such practice you would've never provided that pkg-config stuff :)
      • yalaforge
        what about that ugly LD_LIBRARY_PATH hack? is this from the docs?
      • warp: :-)
      • I'd strongly suggest hardcoding the dynamic linker path using -Wl,-R,/some/path to get rid of LD_LIBRARY_PATH
      • warp
        oh, i use LD_LIBRARY_PATH all the time.
      • yalaforge
        doesn't make it better ;-)
      • warp
        yalaforge: won't hardcoding break stuff when i move the library around?
      • yalaforge
        yup, of course
      • you can set multiple paths though
      • the easiest solution would be to add your library path to /etc/ld.so.conf
      • warp
        yalaforge: for everything in ~/opt, it is in theory a temporary solution until my dist provides whatever i keep in that dir :)
      • yalaforge: root has trouble enough keeping the dist clean of crap just with stuff from packages, i'm not going to introduce home-built stuff on that level.
      • yalaforge
        well, as long as it works for you :-)
      • warp
        it usually does.
      • yalaforge installs stuff in /usr/local, using stow to get rid of it later
      • and when it doesn't, i blame whoever wrote that particular configure.in
      • yalaforge
        did you try stow? might solve your problems a bit easier
      • warp
        not yet, i probably should.
      • can i have it anywhere other than in /usr/local?
      • yalaforge
        yup, I think so
      • yalaforge usually does this:
      • ./configure --prefix=/usr/local/stow/libtunepimp-VERSION
      • make install
      • then go to /usr/local/stow, and type 'stow libtunepimp-VERSION'.
      • with /usr/local/lib in /etc/ld.so.conf, I only have to run ldconfig, and it's usable
      • according to the manpage, you can put your stow directory anywhere. see the '-t' switch
      • zout joined the channel
      • zout
        hi
      • yalaforge
        hey
      • zout
        luks: Sesame Street is cool!
      • luks_
        :)
      • zout
        I was editing it too...
      • warp
        hm, i would probably abuse it and end up with something fairly similar to what i have now :/
      • yalaforge
        yeah, that's possible :-)
      • luks_
        zout: i really don't know what to do about albums like http://musicbrainz.org/album/efa312dd-d70a-43c2...
      • warp
        yalaforge: basically, i want to keep all source-built stuff out of root. so if i log in as a different user, i get the default ubuntu stuff for everything.
      • yalaforge
        hmm, you can use stow for that, too. but that's not the idea behind it.
      • warp
        oh, hey.. i think it worked this time.
      • luks has quit
      • zout
        luks: I'm working on it
      • warp
        yalaforge: i know, so there will not really be any added benefit for using stow
      • yalaforge
        at least you can get rid of installed packages easily. that advantage remains, at least
      • warp
        yalaforge: except a slightly smaller LD_LIBRARY_PATH and such.
      • yalaforge: i can now get rid of installed packages with cd ~/opt; rm PACKAGENAME
      • erm, 'rm -rf' ofcourse :)
      • yalaforge
        for me, it's cd /usr/local/stow && stow -D package-name
      • warp
        configure:21470: result: yes
      • yay!
      • yalaforge
        nice!
      • warp
        that's with:
      • warp [at ararita]:~/usr/src/picard/libtunepimp-0.4.2$ CPPFLAGS=`pkg-config --libs libmusicbrainz` CFLAGS=`pkg-config --cflags libmusicbrainz` CXXFLAGS=`pkg-config --cflags libmusicbrainz` ./configure --prefix=/home/warp/opt/picard
      • yalaforge
        what about the LIBS?
      • warp
        i replaced it with CPPFLAGS