Just a quick note since I'm the reason behind this mess as the SlackBuild's
author...
When I did the actual slackbuild in the first place I used an old centos rpm
as base for how I moved the files around in the final Slackbuild. I cannot
see which at the moment though, as my server and all comp
Grissiom wrote:
Hmm, so many replies when I am sleeping ;) Thanks for caring this issue.
No problem. :-)
Yes, just as Scott
said, there is no "make install" in the tiny official(upstream) Makefile. So
Slackbuild install it manually. The Makefile only builds the binary.
In those cases, look
Hmm, so many replies when I am sleeping ;) Thanks for caring this issue.
Yes, just as Scott
said, there is no "make install" in the tiny official(upstream) Makefile. So
Slackbuild install it manually. The Makefile only builds the binary.
--
Cheers,
Grissiom
___
Scott J. Harmon wrote:
Just my observation from the patch, but it seems that the slackbuild is
manually installing it, indicating that there is no 'make install' (or
that the make install is broken).
Of course, this is just an observation from the patch, I have not looked
at the complete slackb
Robby Workman wrote:
> Patrick J. Volkerding wrote:
>> Grissiom wrote:
>>> Hi all,
>>> The irqbalance could only take into effect only if run as root. So
>>> here is
>>> my patch:
>>
>> Even if something only works for root, IMHO it is better to get
>> upstream to make location changes. That way o
Patrick J. Volkerding wrote:
Grissiom wrote:
Hi all,
The irqbalance could only take into effect only if run as root. So
here is
my patch:
Even if something only works for root, IMHO it is better to get upstream
to make location changes. That way other things (scripts, perhaps)
won't try t
Grissiom wrote:
Hi all,
The irqbalance could only take into effect only if run as root. So here is
my patch:
Even if something only works for root, IMHO it is better to get upstream
to make location changes. That way other things (scripts, perhaps)
won't try to run with an absolute path of /
On Sunday 31 August 2008 09:00:31 pm Robby Workman wrote:
> Robert W. Wendel wrote:
> > I had a problem with libcap 2.11 for 12.1 not compiling.
> > As strang as it may seem, I compiled/installed libcap 1.97 for 12.0
> > . After doing that, then libcap 2.11 for 12.1 compiled successfully.
> >
Robert W. Wendel wrote:
Steve wrote:
On Sunday 31 August 2008 05:20:52 pm Heinz Wiesinger wrote:
Am Sonntag, 17. August 2008 22:09:16 schrieb Robert W. Wendel:
I don't know where to post this so you see it but I'm having
problems
compiling lilypond. I get a compile error:
WARNING: P
On Sun, 31 Aug 2008 20:01:20 -0500
Robby Workman <[EMAIL PROTECTED]>
> Am I missing something obvious?
Yes.
bin != sbin
--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
signature.asc
Description: PGP signature
___
Robby Workman wrote:
> Grissiom wrote:
>> Hi all,
>> The irqbalance could only take into effect only if run as root. So
>> here is my patch:
>> ===
>> --- a/irqbalance.SlackBuild 2008-08-28 14:21:27.0 +0800
>> +++ b/irqbalance.SlackB
Grissiom wrote:
Hi all,
The irqbalance could only take into effect only if run as root. So here
is my patch:
===
--- a/irqbalance.SlackBuild 2008-08-28 14:21:27.0 +0800
+++ b/irqbalance.SlackBuild 2008-08-28 14:22:57.
Robert W. Wendel wrote:
I had a problem with libcap 2.11 for 12.1 not compiling.
As strang as it may seem, I compiled/installed libcap 1.97 for 12.0
. After doing that, then libcap 2.11 for 12.1 compiled successfully.
Removed 1.97 and installed 2.11. Tested the library and 2.11 works ok
Steve wrote:
On Sunday 31 August 2008 05:20:52 pm Heinz Wiesinger wrote:
Am Sonntag, 17. August 2008 22:09:16 schrieb Robert W. Wendel:
I don't know where to post this so you see it but I'm having problems
compiling lilypond. I get a compile error:
WARNING: Please consider installin
[EMAIL PROTECTED] wrote:
On Sunday 31 August 2008 19:02:09 Steve wrote:
Oh well. So, I did build the jack-audio-connector, but I
had to alter the options in the buildscript to exclude capabilities. This
allowed jack to build, and thus rosegarden and ardour, but I'm not certain
things ar
On Sunday 31 August 2008 07:20:53 pm [EMAIL PROTECTED] wrote:
> On Sunday 31 August 2008 19:02:09 Steve wrote:
> Oh well. So, I did build the jack-audio-connector, but I
>
> > had to alter the options in the buildscript to exclude capabilities.
> > This allowed jack to build, and thus rosegarde
On Sunday 31 August 2008 19:02:09 Steve wrote:
Oh well. So, I did build the jack-audio-connector, but I
> had to alter the options in the buildscript to exclude capabilities. This
> allowed jack to build, and thus rosegarden and ardour, but I'm not certain
> things are all fine-and-dandy.
T
On Sunday 31 August 2008 06:51:36 pm Steve wrote:
> Hi list,
>
> Tryinf to build jack-audio-connector-kit which requires libcap. The libcap
> build fails with the following error:
>
> make -C libcap all
> make[1]: Entering directory `/tmp/SBo/libcap-2.11/libcap'
> => making cap_names.c from
> gcc
Hi list,
Tryinf to build jack-audio-connector-kit which requires libcap. The libcap
build fails with the following error:
make -C libcap all
make[1]: Entering directory `/tmp/SBo/libcap-2.11/libcap'
=> making cap_names.c from
gcc -O2 _makenames.c -o _makenames
_makenames.c:10:28: error: sys/ca
On Sunday 31 August 2008 05:20:52 pm Heinz Wiesinger wrote:
> Am Sonntag, 17. August 2008 22:09:16 schrieb Robert W. Wendel:
> >I don't know where to post this so you see it but I'm having problems
> > compiling lilypond. I get a compile error:
> > WARNING: Please consider installing optional
Am Sonntag, 17. August 2008 22:09:16 schrieb Robert W. Wendel:
>I don't know where to post this so you see it but I'm having problems
> compiling lilypond. I get a compile error:
> WARNING: Please consider installing optional programs: kpsewhich
>
> ERROR: Please install required programs: m
21 matches
Mail list logo
