On Thu, 18 Feb 2021, Ricardo J. Barberis wrote:
Not necessarily your mistake, but something's definitely not quite right on
your system.
Ricardo,
That makes many of us.
/usr/local/include/cdda_interface.h:87:31: error: expected ‘:’ before ‘;’
token cdda_private_data_t *private;
In my
[Sent only to the OP a few minutes ago. My mistake]
I assume that you have a not_so_clean Slackware system, with missing or
replaced (non genuine Slackware) packages or added packages conflicting with
the genuine Slackware ones.
This line:
usr/local/include/cdda_interface.h:87:31: error:
On Fri, 19 Feb 2021, at 7:58 AM, Rich Shepard wrote:
> If it's user error I must be at fault, right?
On a clean 14.2 (64-bit) install:
> sbocheck
> sboinstall soundkonverter
and it builds fine. You could check this on a clean install (say in a VM)
before posting for help, at least then you
El Jueves 18/02/2021 a las 20:58, Rich Shepard escribió:
> On Thu, 18 Feb 2021, Didier Spaier wrote:
> > I just typed this as root:
> > sbopkg -r
> > sbopkg -i soundkonverter
> >
> > Took a few minutes to build and install on Slint, based on
> > Slackware64-4.2
>
> Didier,
>
> If it's user error I
On Thu, 18 Feb 2021, Rich Shepard wrote:
/usr/local/include/cdda_interface.h:87:31: error: expected ‘:’ before ‘;’
token
cdda_private_data_t *private;
^
CMakeFiles/soundkonverter.dir/build.make:62: recipe for target
On Thu, 18 Feb 2021, Didier Spaier wrote:
I just typed this as root:
sbopkg -r
sbopkg -i soundkonverter
Took a few minutes to build and install on Slint, based on Slackware64-4.2
Didier,
If it's user error I must be at fault, right?
/usr/local/include/cdda_interface.h:87:31: error:
I meant: based on Slackware64-14.2.
To clarify; the command sbopkg -i builds then install the package in one go.
Le 18/02/2021 à 23:50, Didier Spaier a écrit :
I just typed this as root:
sbopkg -r
sbopkg -i soundkonverter
Took a few minutes to build and install on Slint, based on
I just typed this as root:
sbopkg -r
sbopkg -i soundkonverter
Took a few minutes to build and install on Slint, based on Slackware64-4.2
Then typing as regukar user:
soundkonverter
started it.
Conclusion: no source code error, rather user error.
Didier
Le 18/02/2021 à 23:36, Rich Shepard a
Downloaded both the SlackBuild and the source tarball for soundkonverter and
it fails to build. Looks to me like source code error. Compressed build log
attached.
Rich
soundkonverter-build.log.gz
Description: GNU Zip compressed data
___
Downloaded both the SlackBuild and the source tarball for soundkonverter and
it fails to build. Looks to me like source code error. Compressed build log
attached.
Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
On Thu, 18 Feb 2021, Jeremy Hansen wrote:
This is likely something that's in the source tarball and resides in the
/tmp/SBo/atlas-$VERSION directory. It wouldn't be something on SBo if it's
referenced by the source itself.
Jeremy,
Which is another reason to ignore it since there is an
On Thu, Feb 18, 2021, 1:04 PM Rich Shepard wrote:
> On Thu, 18 Feb 2021, Erich Ritz wrote:
>
> > Perhaps it meant to reference this?
> >
> https://slackbuilds.org/slackbuilds/14.2/libraries/atlas/README.SLACKWARE
> > which instructs you to do:
> > /etc/rc.d/rc.cpufreq performance
>
> Erich,
>
>
On Thu, 18 Feb 2021, Ricardo J. Barberis wrote:
If you already use sbopkg to update your packages, you can also use it to
install new packages:
$ sudo sbopkg -i "package-name"
It won't install dependencies (you can use sqg as suggested elsewhere) but at
least you won't have to manually
El Jueves 18/02/2021 a las 10:40, Rich Shepard escribió:
> On Thu, 18 Feb 2021, B Watson wrote:
> > You might want to use git to track changes to the repo.
>
> Every week after updates are posted I run sbopkg and update what's
> installed. Now I'm installing removed packages which is not automated
On Thu, 18 Feb 2021, Erich Ritz wrote:
Perhaps it meant to reference this?
https://slackbuilds.org/slackbuilds/14.2/libraries/atlas/README.SLACKWARE
which instructs you to do:
/etc/rc.d/rc.cpufreq performance
Erich,
I saw the README.SLACKWARE file but was looking for the INSTALL.txt file the
Hi Rich,
‐‐‐ Original Message ‐‐‐
On Thursday, February 18, 2021 11:38 AM, Rich Shepard
wrote:
> The hardware has an AMD Ryzen7 2700 (8 cores/16 threads) and 32G RAM. I'm
> trying to build atlas but it bails out because of throttling and references
> its INSTALL.txt which I cannot
The hardware has an AMD Ryzen7 2700 (8 cores/16 threads) and 32G RAM. I'm
trying to build atlas but it bails out because of throttling and references
its INSTALL.txt which I cannot find. The (compressed) build log is attached.
I don't overclock and I hesitate to mess with the clock speed.
I've
Does sync find packages I need that are not already installed? I was
under
the impression that when I ran sync it compared the SBo packages here
with
those on the SBo repo.
no, what it does is rsync your script repo with the public sbo (script)
repo, so all your sbo local slackbuild
On Thu, 18 Feb 2021, Jeremy Hansen wrote:
All sbopkg's sync does is sync its local repo with SBo's online repo.
Jeremy,
I know that and have been using it that way for a long time.
However, since sbopkg itself doesn't track dependencies (that is kinda done
with sqg),
Aha! I knew there
On Thu, Feb 18, 2021, 8:03 AM Rich Shepard wrote:
> On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:
>
> > if you had run "sync" from within sbopkg as you just said, your
> > geoclue2.SlackBuild would have been the most up-to-date one, and you
> would
> > have avoided the problem
On Wed, 17 Feb 2021, Jeremy Hansen wrote:
If you're going to build packages manually, it would probably be good to
keep a local git repo of SBo and update that before running SlackBuilds.
You can create the repo by running:
git clone git://git.slackbuilds.org/slackbuilds.git sbo-repo
Then you
On Thu, 18 Feb 2021, Tim Dickson via SlackBuilds-users wrote:
if you had run "sync" from within sbopkg as you just said, your
geoclue2.SlackBuild would have been the most up-to-date one, and you would
have avoided the problem you had, which makes it puzzling.
Tim,
Does sync find packages I
see inline comment.
On 18/02/2021 13:40, Rich Shepard wrote:
On Thu, 18 Feb 2021, B Watson wrote:
*Please* try to avoid doing this. Before you send a mail to the list
asking for help with a problem, make sure the problem hasn't already
been fixed in the repo. We can't guess if you're using
On Thu, 18 Feb 2021, B Watson wrote:
*Please* try to avoid doing this. Before you send a mail to the list
asking for help with a problem, make sure the problem hasn't already
been fixed in the repo. We can't guess if you're using outdated stuff
from 3 years ago, so we collectively wasted
24 matches
Mail list logo
