Prev: EPI score for ICELAND is overrated.
Next: Domain Thief Lew Pitcher
From: Grant on 17 Mar 2010 07:00
On Wed, 17 Mar 2010 09:23:38 +0000, xtd8865(a)gmail.com (.Martin.) wrote:

>Grant <omg(a)grrr.id.au> writes:
>
>> On Wed, 17 Mar 2010 07:22:52 +0000, xtd8865(a)gmail.com (.Martin.) wrote:
>>
>>>Grant <omg(a)grrr.id.au> writes:
>>>
>>>> On Wed, 17 Mar 2010 01:27:07 +0000, Martin <xtd8865(a)gmail.com> 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
>>>>
>>>> Is the above the first warning or error message?
>>>>
>>>> Grant.
>>>
>>>Yep, that's the first warning/error.
>>
>> I got an error trying to build the libmp4v2 from SBo, so I give up,
>> can't install the library :(
>>
>> configure: error: in `/tmp/SBo/mp4v2-1.9.1':
>> configure: error: C++ compiler cannot create executables
>> See `config.log' for more details.
>>
>> and the config.log doesn't mention anything more useful. Full install
>> of slack64-13.0 with patches.
>>
>> Sorry, cannot get near your issue.
>>
>> Grant.
>
>Thanks for your time, Grant.
>Are you using the right ARCH when compilint libmp4v2?
>I remember I had something like that when (by mistake) I was
>trying to install i486 on x86_64 (or vice versa, don't remember).

Ah, I didn't check, guess I expected the SBo script to look after that
sort of thing.

I may try again tomorrow, I just had a quick try to duplicate your problem.
>
>My systems are: fully up-to-date 64-current and a freshly installed and
>patched 64-13 with very few additional slackbuilds.
>I was looking for some patches on the internet. I found one but it was
>relevant to slack 11.2 and did not even patch properly.

Okay.

Grant.
From: Sylvain Robitaille on 17 Mar 2010 11:08
Grant wrote:

>> Are you using the right ARCH when compilint libmp4v2?
>> ...
>
> Ah, I didn't check, guess I expected the SBo script to look after that
> sort of thing.

.... another argument for having SlackBuild scripts auto-detect $ARCH by
default ... I gather (but have not verified) that those scripts in the
distribution are doing that now. Folks maintaining scripts for various
repositories should fix their scripts ... (and yes, I realize that's a
major undertaking, but that's what maintaining these scripts for a
repository is ...)

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
From: King Beowulf on 18 Mar 2010 22:10
On Wed, 17 Mar 2010 15:08:55 +0000, Sylvain Robitaille wrote:

> Grant wrote:
>
-----snip------
>
> ... another argument for having SlackBuild scripts auto-detect $ARCH by
> default ...
------snip---

Horrors to that thought. There's nothing wrong woth taking a bit of
initiative and checking the slackbuild yourself...assuming you can figure
out what arch you have!

besides, some of us have converted Slackware64-13 to multilib, and we DO
NOT want any sort of autodetection...

From: Sylvain Robitaille on 19 Mar 2010 00:16
King Beowulf wrote:

>> Grant wrote:

That was me, actually ...

>> ... another argument for having SlackBuild scripts auto-detect $ARCH by
>> default ...
>
> Horrors to that thought. There's nothing wrong woth taking a bit of
> initiative and checking the slackbuild yourself...assuming you can
> figure out what arch you have!

That's an important assumption, don't you think? Are you suggesting
that folks who don't know, or don't know how to find out, or don't know
how to use that value shouldn't be able to install software themselves?

> besides, some of us have converted Slackware64-13 to multilib, and we
> DO NOT want any sort of autodetection...

So override the auto-detected value. If you know enough to get as far
as you're describing, overriding the value at build-time should be
trivial. The same is true for folks cross-compiling for a different
architecture: those folks will know how to override the value. There's
no need to change any content of the script, using the method of setting
the auto-detected value that I've already proposed, and a similar
method, which I believe that new build scripts included in Slackware
use.

"auto-detection" does not mean "inflexible". What it means is that for
probably better than ninety percent of users, ninety percent of the
time, it will be easier for those users to have the same script produce
correct results without requiring any human intervention, and with less
chance of error caused by copying and pasting, or typos, etc. I happen
to think that's a good thing ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
From: Martin on 19 Mar 2010 03:16
On 03/19/2010 04:16 AM, Sylvain Robitaille wrote:
> King Beowulf wrote:
>
>>> Grant wrote:
>
> That was me, actually ...
>
>>> ... another argument for having SlackBuild scripts auto-detect $ARCH by
>>> default ...
>>
>> Horrors to that thought. There's nothing wrong woth taking a bit of
>> initiative and checking the slackbuild yourself...assuming you can
>> figure out what arch you have!
>
> That's an important assumption, don't you think? Are you suggesting
> that folks who don't know, or don't know how to find out, or don't know
> how to use that value shouldn't be able to install software themselves?
>
>> besides, some of us have converted Slackware64-13 to multilib, and we
>> DO NOT want any sort of autodetection...
>
> So override the auto-detected value. If you know enough to get as far
> as you're describing, overriding the value at build-time should be
> trivial. The same is true for folks cross-compiling for a different
> architecture: those folks will know how to override the value. There's
> no need to change any content of the script, using the method of setting
> the auto-detected value that I've already proposed, and a similar
> method, which I believe that new build scripts included in Slackware
> use.
>
> "auto-detection" does not mean "inflexible". What it means is that for
> probably better than ninety percent of users, ninety percent of the
> time, it will be easier for those users to have the same script produce
> correct results without requiring any human intervention, and with less
> chance of error caused by copying and pasting, or typos, etc. I happen
> to think that's a good thing ...
>


I got used to modifying the $ARCH variable - so I don't mind. 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.

Coming back to the OP, any ideas on my gtkpod error?
Can anyone confirm that they've managed to install mp4v2 + gtkpod
without any modifications/patches on slack64 13 or -current?

thank you

--
regards

Martin
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: EPI score for ICELAND is overrated.
Next: Domain Thief Lew Pitcher