From: Sylvain Robitaille on 19 Mar 2010 10:28 Martin wrote: > .... It also turns out that sometimes it's not enough to just 'su' to > successfully build a slackbuild, you need to 'su -' to get the > complete root's environment. At least that's the case on my system. Odd. I don't see that on my systems. > Coming back to the OP, any ideas on my gtkpod error? It seems to not find your installation of libmp4v2 ... You installed that manually? With SBo script? In an odd location? > Can anyone confirm that they've managed to install mp4v2 + gtkpod > without any modifications/patches on slack64 13 or -current? Sorry ... -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: notbob on 19 Mar 2010 10:58 On 2010-03-19, Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > Martin wrote: > >> .... It also turns out that sometimes it's not enough to just 'su' to >> successfully build a slackbuild, you need to 'su -' to get the >> complete root's environment. At least that's the case on my system. > > Odd. I don't see that on my systems. I don't think it makes too much differece unless one has custom bash settings for root. For example, my root prompt is bright red to warn me I could do mad mojo if not careful, or it doesn't take you to /root when you invoke no arg 'cd'. Small stuff like that. Otherwise it still has that magical root power. ;) nb
From: Martin on 20 Mar 2010 07:36 On 03/19/2010 02:28 PM, Sylvain Robitaille wrote: > Martin wrote: > >> .... It also turns out that sometimes it's not enough to just 'su' to >> successfully build a slackbuild, you need to 'su -' to get the >> complete root's environment. At least that's the case on my system. > > Odd. I don't see that on my systems. Actually It happened only once or twice. I think it was auctex. I gave me some errors while building it through sbopkg. It was related to the fact that it couldn't find latex on my system, which was weird as I did have all the necessary packages installed. When I did 'su -' it found it without problems. > >> Coming back to the OP, any ideas on my gtkpod error? > > It seems to not find your installation of libmp4v2 ... You installed > that manually? With SBo script? In an odd location? > >> Can anyone confirm that they've managed to install mp4v2 + gtkpod >> without any modifications/patches on slack64 13 or -current? > > Sorry ... > Thanks I installed libmp4v2 via sbopkg. It didn't give me any errors. gtkpod installs fine if I remove libmp4v2. The problem is that I'd like to have mp4 support. -- regards Martin
From: King Beowulf on 25 Mar 2010 02:40 On Wed, 17 Mar 2010 01:27:07 +0000, Martin wrote: > I'm trying to install gtkpod from slackbuilds. I've installed libmp4v2 > and try to get gtkpod slackbuild to install: that's what I get: > >> 0 -lgmodule-2.0 -lglib-2.0 -lcurl -pthread -lgnomevfs-2 -lgconf-2 >> -lgthread-2.0 -lrt -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -lhal >> -ldbus-1 -lpthread -lrt mp4file.o: In function `mp4_write_file_info': >> mp4file.c:(.text+0x8f): undefined reference to `MP4GetMetadataBPM' >> mp4file.c:(.text+0x144): undefined reference to >> `MP4SetMetadataComposer' mp4file.c:(.text+0x18f): undefined reference >> to `MP4SetMetadataReleaseDate' mp4file.c:(.text+0x1f3): undefined >> reference to `MP4SetMetadataBPM' mp4file.c:(.text+0x30b): undefined >> reference to `MP4SetMetadataBPM' mp4file.o: In function >> `mp4_get_file_info': mp4file.c:(.text+0xa99): undefined reference to >> `MP4GetMetadataComposer' mp4file.c:(.text+0xb03): undefined reference >> to `MP4GetMetadataReleaseDate' mp4file.c:(.text+0xc56): undefined >> reference to `MP4GetMetadataBPM' collect2: ld returned 1 exit status >> make[2]: *** [gtkpod] Error 1 >> make[2]: Leaving directory `/tmp/SBo/gtkpod-0.99.14/src' make[1]: *** >> [all-recursive] Error 1 >> make[1]: Leaving directory `/tmp/SBo/gtkpod-0.99.14' make: *** [all] >> Error 2 > It happens both on slackware64-13 and slackware64-current Since I just use mp3 this wasn't an issue for me. But now its a "mystery" but lo and behold, I just checked today and there is a new SBo script with patch to fix this error. It compiles fine now on my Slackware64 13.0 but I haven't yet tested functionality.
From: .Martin. on 25 Mar 2010 18:33
King Beowulf <kingbeowulf(a)gmail.com> writes: > On Wed, 17 Mar 2010 01:27:07 +0000, Martin wrote: > >> I'm trying to install gtkpod from slackbuilds. I've installed libmp4v2 >> and try to get gtkpod slackbuild to install: that's what I get: >> >>> 0 -lgmodule-2.0 -lglib-2.0 -lcurl -pthread -lgnomevfs-2 -lgconf-2 >>> -lgthread-2.0 -lrt -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -lhal >>> -ldbus-1 -lpthread -lrt mp4file.o: In function `mp4_write_file_info': >>> mp4file.c:(.text+0x8f): undefined reference to `MP4GetMetadataBPM' >>> mp4file.c:(.text+0x144): undefined reference to >>> `MP4SetMetadataComposer' mp4file.c:(.text+0x18f): undefined reference >>> to `MP4SetMetadataReleaseDate' mp4file.c:(.text+0x1f3): undefined >>> reference to `MP4SetMetadataBPM' mp4file.c:(.text+0x30b): undefined >>> reference to `MP4SetMetadataBPM' mp4file.o: In function >>> `mp4_get_file_info': mp4file.c:(.text+0xa99): undefined reference to >>> `MP4GetMetadataComposer' mp4file.c:(.text+0xb03): undefined reference >>> to `MP4GetMetadataReleaseDate' mp4file.c:(.text+0xc56): undefined >>> reference to `MP4GetMetadataBPM' collect2: ld returned 1 exit status >>> make[2]: *** [gtkpod] Error 1 >>> make[2]: Leaving directory `/tmp/SBo/gtkpod-0.99.14/src' make[1]: *** >>> [all-recursive] Error 1 >>> make[1]: Leaving directory `/tmp/SBo/gtkpod-0.99.14' make: *** [all] >>> Error 2 >> It happens both on slackware64-13 and slackware64-current > > Since I just use mp3 this wasn't an issue for me. But now its a > "mystery" but lo and behold, I just checked today and there is a new SBo > script with patch to fix this error. It compiles fine now on my > Slackware64 13.0 but I haven't yet tested functionality. Excellent news - I'm going to try it later on. Thanks for letting me know. -- regards Martin |