Re: [Slackbuilds-users] mozilla-firefox

[Habs]

On Fri, 31 May 2024, Jude DaShiell wrote:


Has checksum mismatch.


--
Jude 


hello - is that a  package on slackbuilds.org !
perhaps provide a link

habs
--- Sent using Alpine/Pine, probably the best MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] sbotools config issues

[Habs]

On Sun, 10 Mar 2024, J. Milgram wrote:



Hello.

Once again having problems installing with sbotools. There's evidently some 
config subtlety I'm not grasping, hopefully someone can set me straight.


I have a fresh -current install and am using the default 15.0 repo. Many 
slackbuilds installed fine, but then:


/usr/sbin/sboinstall XXX fails with:

"Unable to locate XXX in the SlackBuilds.org tree."

Where XXX is in [ python3-build, python3-wheel ] ... and maybe others. May be 
just python3 packages that fail but haven't investigated. I do see these 
slackbuilds in the slackbuilds repo so they're not mirages.


Some config stuff:


cat /etc/slackware-version

Slackware 15.0+


cat /etc/sbotools/sbotools.conf

JOBS=5
DISTCLEAN=TRUE




good morning all

Perhaps using REPO in the conf e.g.:

REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git

That sorted a few issues out in a similar case.  sbofind/install/etc all 
work fine with it set.


Habs
--- Sent using Alpine/Pine, probably the best MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] I would like librsync and rdiff-backup updated (to 2.3.2 and 2.0.5 respectively)

[Habs]

On Sat, 17 Dec 2022, isaac...@isaacyu1.com wrote:



Hi Ricardo,

In that case, I'll update and take over maintenance of librsync.
Eugen, would you like to take over maintenance of rdiff-backup? If not, I'll 
upload the update to rdiff-backup (and then orphan rdiff-backup).

In a few days, after we (Ricardo, Eugen and I) finalize maintainership 
decisions, I will make the pull requests on the SlackBuilds github:
https://github.com/SlackBuildsOrg/slackbuilds

- Isaac

On Friday, December 16, 2022 16:18 PST, "Ricardo J. Barberis" 
 wrote:
 Hi everyone, sorry for my belated reply.

I have (and am using for the past year or so) librsync 2.3.0 and rdiff-backup
2.0.5 on Slackware64 -current. I have my slackbuilds at [0] and [1].

Unfortunately I don't have much time to keep maintaining my slackbuilds
anymore, and I'll probably stop using Slackware altogether in the near future,
so feel free to take over maintenance of these two slackbuilds if you can.


It may seem impertinent to ask, but it is difficult to fathom :-), why the 
probability in stopping using Slackware altogether ?


Habs
--- Sent using Alpine/Pine, probably the best MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] extra files in $PKG/install

[Habs]

On Mon, 11 Apr 2022, B. Watson wrote:



Sorry, this turned out to be longer than I expected. But I think it
covers the issue in enough detail that it's worth it...

On Mon, 11 Apr 2022, Giancarlo Dessì wrote:

I think this could be a singular issue in your system. I have built 
hudrends of different slackbuilds but no files like these exist (I searched 
in / and in /tmp/SBo). Sometimes I check and empty the directory but I 
never found files like these.


You wouldn't have seen this on Slackware 14.2 or earlier; it's caused
by a change to installpkg that happened in 2018 (so you might have
seen it on pre-15.0 -current, if you ran that).

It's happened on two different 15.0 systems here. It's not a problem
with my setup, it's a problem with a few specific SlackBuilds. So far,
I've discovered it in:

multimedia/l-smash
network/ipxnet
system/freeipmi



good day folks

finding all SlackBuild files (on the repo snap created by sbotools) and 
then some grotty line grep and sed stuff on each SlackBuild, reveals only 
those three builds mentioned above having anything other than slack-desc, 
doinst.sh or douninst.sh put in '$PKG/install'.


it was a basic attempt to get a rough picture on this issue reported, so 
some 'may have got through' the sift.


regards
Habs

grep pattern  '>$PKG/install/' or '> $PKG/install/'

sed patterm   '/slack-desc$\|doinst\.sh$\|douninst\.sh$/ d'


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Fri, 8 Apr 2022, Luc Van Rompaey wrote:


Op vr 8 apr. 2022 om 14:18 schreef Luc Van Rompaey 
:





Op wo 6 apr. 2022 om 14:49 schreef Habs :


On Wed, 6 Apr 2022, Luc Van Rompaey wrote:


Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org>:


java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7

but

got 0xc7a06d31)


This looks like you're inadvertently using the wrong set of source
files. Each new openjdk version has a new set of source files, many

of

which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
your build system can easily pick up the wrong source file.

chris


Good morning all

I do not doubt the comment above, but in this case, how could it be

unless

the slackbuild source links are out of step/compromised/whatever.

As I mentioned, it is a clean physical machine freshly installed and

then

updated - no other [java related or other slackbuild addons etc]

downloads

prior - and simply the source files linked in the slackbuild info.

Each

slackbuild individually run using 'su -' (rather than using sbotools

or

similar) as required.  I don't even get to try openjdk8 (or download
anything for it) as apache-ant, gcc5 and openjdk7 are listed as

required

first.  It is openjdk7 that is failing in that chain as such.

That all said, I will go back and check the sources, though I think

that

has been done by Matteo.

Regards
Habs


My comment will not add much to the problem, but my several tries are

all

failing at the same place (ie: invalid entry CRC).
Be it on my master very unclean multilib box, a chroot, multilib or

not,

updated and clean, or some other cleaner boxes, VMs, not multilib, I

can't

make it build, and it always fails on the same place...

But unlike others here, I don't pretend doing it on perfectly clean
installations (though always without any other java installed).
Although I am really sure my source packages are the right ones, MD5SUM
checked and all.

--
Arnaud 

Let me first tell you all that I have been out of the Slackware loop

for a

while and that I'm only just getting ready to install Slackware 15.0 on

my

new computer.
Thus, for now, I cannot do any tests involving Slackware myself.

Anyway, I remember looking into the different Apache Ant releases just
before life interfered, and I was about to try and figure out how the

Ant

releases and the (Open)JDK version did and did not go together. I hadn't
gotten far enough to draw any final conclusions, though, and I hadn't

taken

any meaningful notes yet.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


This ongoing discussion reminded me that I had sent in an update to the
apache-ant slackbuild when I took it over. According to the SlackBuilds
history, it had been at Ant version 1.9.9 until then, and I updated it

to

1.9.14. Now, if I remember correctly, I had successfully compiled

OpenJDK 7

(and subsequently 8) before I took over the apache-ant slackbuild, and I
don't believe that I have ever recompiled them since then.

Anyway, to cut a long story short, I'm now wondering if, perhaps, the
problem may have anything to do with the Apache Ant version. In other
words, the build fails with Ant 1.9.14, but it may still complete
successfully with Ant 1.9.9. May be worth a try. Then, if that works, I

may

attempt a build with the latest Ant 1.9.x revision (currently 1.9.16)

and

see what gives. In any case, there's no point in trying the build with

Ant

1.10.x, since that cannot make sense of any Java run-time environment

older

than, I think, Java version 8 (and, consequently, the Java environment
provided by gcc5).

If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
from https://archive.apache.org/dist/ant/binaries/

Let's hope we can work this issue out.

Regards,
Luc.


Good day all

I can confirm that using 1.9.9 does not resolve the issue from my attempt
a short while ago.

Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:

9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



I have just successfully built openjdk7 on a freshly installed Slackware64
15.0 system, with no system updates installed yet.
The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
I'm using a 24-GB

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Fri, 8 Apr 2022, Luc Van Rompaey wrote:


Op wo 6 apr. 2022 om 14:49 schreef Habs :


On Wed, 6 Apr 2022, Luc Van Rompaey wrote:


Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org>:


java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7

but

got 0xc7a06d31)


This looks like you're inadvertently using the wrong set of source
files. Each new openjdk version has a new set of source files, many of
which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
your build system can easily pick up the wrong source file.

chris


Good morning all

I do not doubt the comment above, but in this case, how could it be

unless

the slackbuild source links are out of step/compromised/whatever.

As I mentioned, it is a clean physical machine freshly installed and

then

updated - no other [java related or other slackbuild addons etc]

downloads

prior - and simply the source files linked in the slackbuild info.

Each

slackbuild individually run using 'su -' (rather than using sbotools or
similar) as required.  I don't even get to try openjdk8 (or download
anything for it) as apache-ant, gcc5 and openjdk7 are listed as

required

first.  It is openjdk7 that is failing in that chain as such.

That all said, I will go back and check the sources, though I think

that

has been done by Matteo.

Regards
Habs


My comment will not add much to the problem, but my several tries are

all

failing at the same place (ie: invalid entry CRC).
Be it on my master very unclean multilib box, a chroot, multilib or not,
updated and clean, or some other cleaner boxes, VMs, not multilib, I

can't

make it build, and it always fails on the same place...

But unlike others here, I don't pretend doing it on perfectly clean
installations (though always without any other java installed).
Although I am really sure my source packages are the right ones, MD5SUM
checked and all.

--
Arnaud 

Let me first tell you all that I have been out of the Slackware loop

for a

while and that I'm only just getting ready to install Slackware 15.0 on

my

new computer.
Thus, for now, I cannot do any tests involving Slackware myself.

Anyway, I remember looking into the different Apache Ant releases just
before life interfered, and I was about to try and figure out how the Ant
releases and the (Open)JDK version did and did not go together. I hadn't
gotten far enough to draw any final conclusions, though, and I hadn't

taken

any meaningful notes yet.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


This ongoing discussion reminded me that I had sent in an update to the
apache-ant slackbuild when I took it over. According to the SlackBuilds
history, it had been at Ant version 1.9.9 until then, and I updated it to
1.9.14. Now, if I remember correctly, I had successfully compiled

OpenJDK 7

(and subsequently 8) before I took over the apache-ant slackbuild, and I
don't believe that I have ever recompiled them since then.

Anyway, to cut a long story short, I'm now wondering if, perhaps, the
problem may have anything to do with the Apache Ant version. In other
words, the build fails with Ant 1.9.14, but it may still complete
successfully with Ant 1.9.9. May be worth a try. Then, if that works, I

may

attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
see what gives. In any case, there's no point in trying the build with

Ant

1.10.x, since that cannot make sense of any Java run-time environment

older

than, I think, Java version 8 (and, consequently, the Java environment
provided by gcc5).

If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
from https://archive.apache.org/dist/ant/binaries/

Let's hope we can work this issue out.

Regards,
Luc.


Good day all

I can confirm that using 1.9.9 does not resolve the issue from my attempt
a short while ago.

Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:

9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/



I have just successfully built openjdk7 on a freshly installed Slackware64
15.0 system, with no system updates installed yet.
The apache-ant version is 1.9.14 (as currently provided by the slackbuild).
I'm using a 24-GB tmpfs for the "/tmp" location.

I will next update the Sl

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Wed, 6 Apr 2022, Lenard Spencer wrote:


Since openjdk6 and 7 can no longer be built at this time, I would have to
say drop them for now.  openjdk8 can be built if you have zulu-openjdk7
installed and adjust BOOT_JAVA to point to /usr/lib(64)/zulu-openjdk7 in
the script.



good day all

Just on the off-chance, I decided to have another go this morning.

Openjdk7  build completed.

So to clarify between previous and this successul attempt:

Previously, immediately after installing slackware 15, I ran 'slackpkg 
upgrade-all' to bring the release up to latest changes.


Then I left it running and moved onto a laptop I used and connected up to 
it remotely using ssh.


Then I tried the openjdk7 build.  Four attempts (inc reinstall Slack 15 
plus upgrade plus tweaks suggested on here for the build) failed.


For this mornings successful build of openjdk7 I reinstalled slackware 
just as previous, but I did *not* update it (slackpkg upgrade-all).


Nor did I use 'ssh' and just did the build at the console.

So the differences are 1) I was at a console on the machine and not via 
ssh and 2) I did not run 'slackpkg upgrade-all' (which installs a new 
kernel etc) following the install.


Perhap in these two differences is a/the reason.

- environment of ssh (which I doubt is an issue as it's never been a 
problem previously so why with Slack.15)


- 'slackpkg upgrade-all' is introducing an 'incompatibility' issue (eg. 
perhaps with gcc5 ?)



It's all I have at my level of competency  .

Regards
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Wed, 6 Apr 2022, Luc Van Rompaey wrote:


Op wo 6 apr. 2022 om 10:10 schreef Arnaud via SlackBuilds-users <
slackbuilds-users@slackbuilds.org>:


java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
got 0xc7a06d31)


This looks like you're inadvertently using the wrong set of source
files. Each new openjdk version has a new set of source files, many of
which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
your build system can easily pick up the wrong source file.

chris


Good morning all

I do not doubt the comment above, but in this case, how could it be

unless

the slackbuild source links are out of step/compromised/whatever.

As I mentioned, it is a clean physical machine freshly installed and

then

updated - no other [java related or other slackbuild addons etc]

downloads

prior - and simply the source files linked in the slackbuild info.  Each
slackbuild individually run using 'su -' (rather than using sbotools or
similar) as required.  I don't even get to try openjdk8 (or download
anything for it) as apache-ant, gcc5 and openjdk7 are listed as required
first.  It is openjdk7 that is failing in that chain as such.

That all said, I will go back and check the sources, though I think that
has been done by Matteo.

Regards
Habs


My comment will not add much to the problem, but my several tries are all
failing at the same place (ie: invalid entry CRC).
Be it on my master very unclean multilib box, a chroot, multilib or not,
updated and clean, or some other cleaner boxes, VMs, not multilib, I can't
make it build, and it always fails on the same place...

But unlike others here, I don't pretend doing it on perfectly clean
installations (though always without any other java installed).
Although I am really sure my source packages are the right ones, MD5SUM
checked and all.

--
Arnaud 

Let me first tell you all that I have been out of the Slackware loop for a

while and that I'm only just getting ready to install Slackware 15.0 on my
new computer.
Thus, for now, I cannot do any tests involving Slackware myself.

Anyway, I remember looking into the different Apache Ant releases just
before life interfered, and I was about to try and figure out how the Ant
releases and the (Open)JDK version did and did not go together. I hadn't
gotten far enough to draw any final conclusions, though, and I hadn't taken
any meaningful notes yet.

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/


This ongoing discussion reminded me that I had sent in an update to the
apache-ant slackbuild when I took it over. According to the SlackBuilds
history, it had been at Ant version 1.9.9 until then, and I updated it to
1.9.14. Now, if I remember correctly, I had successfully compiled OpenJDK 7
(and subsequently 8) before I took over the apache-ant slackbuild, and I
don't believe that I have ever recompiled them since then.

Anyway, to cut a long story short, I'm now wondering if, perhaps, the
problem may have anything to do with the Apache Ant version. In other
words, the build fails with Ant 1.9.14, but it may still complete
successfully with Ant 1.9.9. May be worth a try. Then, if that works, I may
attempt a build with the latest Ant 1.9.x revision (currently 1.9.16) and
see what gives. In any case, there's no point in trying the build with Ant
1.10.x, since that cannot make sense of any Java run-time environment older
than, I think, Java version 8 (and, consequently, the Java environment
provided by gcc5).

If anyone wants to try out the OpenJDK build with Apache Ant 1.9.9 while
I'm getting ready for Slackware 15.0, the Ant versions can be downloaded
from https://archive.apache.org/dist/ant/binaries/

Let's hope we can work this issue out.

Regards,
Luc.


Good day all

I can confirm that using 1.9.9 does not resolve the issue from my attempt 
a short while ago.


Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Wed, 6 Apr 2022, Christoph Willing wrote:


On 6/4/22 06:00, Habs wrote:

java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
got 0xc7a06d31)


This looks like you're inadvertently using the wrong set of source
files. Each new openjdk version has a new set of source files, many of
which have no version number (openjdk.tar.bz2, corba.tar.bz2, ...) so
your build system can easily pick up the wrong source file.

chris


Good morning all

I do not doubt the comment above, but in this case, how could it be unless 
the slackbuild source links are out of step/compromised/whatever.


As I mentioned, it is a clean physical machine freshly installed and then 
updated - no other [java related or other slackbuild addons etc] downloads 
prior - and simply the source files linked in the slackbuild info.  Each 
slackbuild individually run using 'su -' (rather than using sbotools or 
similar) as required.  I don't even get to try openjdk8 (or download 
anything for it) as apache-ant, gcc5 and openjdk7 are listed as required 
first.  It is openjdk7 that is failing in that chain as such.


That all said, I will go back and check the sources, though I think that 
has been done by Matteo.


Regards
Habs


___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Tue, 5 Apr 2022, Habs wrote:


On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:


Starting afresh - clean [physical] machine Slackware 15 64 then
update-all (slackpkg) - same 'result'; same error and drops out at the
openjdk7 build just as before.


Just to make sure
did you run "su -" instead of just "su" ?


yes - in fact, with and without.

As an aside, I have run these openjdk's before (without '-') and had no 
problems.  I will rerun the whole chain again (with the '-') to make sure and 
clean out beforehand.


Having said that, the error has been the same and the machine rebuilt twice 
now to be 'clean' before starting. It's started happening fairly recently, as 
prior, all was well.


One wonders if the  recent slackpkg updates have introduced something.  It 
has never been this flaky previously for me.



Will post again when I've had another go.




Right then.  I've had another do (and using 'su -') and its the same 
result.  openjdk7 fails as reported by Matteo and myself.


Perhaps there is a setting somewhere I'm missing. Perhaps a new 
incompatibility somewhere since the slackbuild was packaged.


I can't fathom why it's fine on a VM as has been reported, but on this 
[physical] machine, all I have tried (inc. two rebuilds for a clean 
machine) has not resulted in a successful build.


As I say, it has worked previously, but not now.

Here again is the last few bits of the openjdk7 build log until it bails.

/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes 
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got 
0xc7a06d31)

at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at sun.tools.jar.Main.copy(Main.java:822)
at sun.tools.jar.Main.update(Main.java:584)
at sun.tools.jar.Main.run(Main.java:224)
at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86: 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar] 
Error 1
gmake[8]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64: 
all] Error 2
gmake[7]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103: 
sa_stuff] Error 2
gmake[6]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323: 
product] Error 2
gmake[5]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'

gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'

gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'

gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2



Regards and thank you
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:


Starting afresh - clean [physical] machine Slackware 15 64 then
update-all (slackpkg) - same 'result'; same error and drops out at the
openjdk7 build just as before.


Just to make sure
did you run "su -" instead of just "su" ?


yes - in fact, with and without.

As an aside, I have run these openjdk's before (without '-') and had no 
problems.  I will rerun the whole chain again (with the '-') to make sure 
and clean out beforehand.


Having said that, the error has been the same and the machine rebuilt 
twice now to be 'clean' before starting. It's started happening fairly 
recently, as prior, all was well.


One wonders if the  recent slackpkg updates have introduced something.  It 
has never been this flaky previously for me.



Will post again when I've had another go.

Thank you
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Tue, 5 Apr 2022, Habs wrote:


On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:


Perhaps I should have mentioned in my OP, it is a clean Slackware 15
64bit machine, just freshly installed and fully updated on April 3rd,
before starting the openjdk8 build (ie. installing gcc5, apache-ant
openjdk7 and lastly openjdk8).  It baulks at openjdk7 with errors as
detailed in the OP.

The build was tried manually  and using sbotools. Same result.


I just tested openjdk8 on a clean VM and it built just fine using sbopkg

openjdk8:
 MD5SUM check for icedtea-3.20.0.tar.xz ... OK
 MD5SUM check for openjdk.tar.xz ... OK
 MD5SUM check for corba.tar.xz ... OK
 MD5SUM check for jaxp.tar.xz ... OK
 MD5SUM check for jaxws.tar.xz ... OK
 MD5SUM check for jdk.tar.xz ... OK
 MD5SUM check for langtools.tar.xz ... OK
 MD5SUM check for nashorn.tar.xz ... OK
 MD5SUM check for hotspot.tar.xz ... OK
 Building package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
 Installing package openjdk8-8u292-x86_64-1_SBo.tgz ... OK

openjdk7 also built just fine as that's the requirement to build openjdk8


--
Willy Sudiarto Raharjo



Yes I noted from your earlier message you had success in a VM.

The physical machine platform I used was not so.  Strange.

I will take the hit and strip it and have another go and see what happens.

Essentially just repeating earlier what I did earlier, repartition disk etc, 
Install Slackware 15 64, update it using 'update-all' (slackpkg) then install 
gcc5, apache-ant, openjdk7, openjdk8 using the packages on 'slackbuilds'.






Starting afresh - clean [physical] machine Slackware 15 64 then update-all 
(slackpkg) - same 'result'; same error and drops out at the openjdk7 build 
just as before.



Regards
Habs

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

On Tue, 5 Apr 2022, Willy Sudiarto Raharjo wrote:


Perhaps I should have mentioned in my OP, it is a clean Slackware 15
64bit machine, just freshly installed and fully updated on April 3rd,
before starting the openjdk8 build (ie. installing gcc5, apache-ant
openjdk7 and lastly openjdk8).  It baulks at openjdk7 with errors as
detailed in the OP.

The build was tried manually  and using sbotools. Same result.


I just tested openjdk8 on a clean VM and it built just fine using sbopkg

openjdk8:
 MD5SUM check for icedtea-3.20.0.tar.xz ... OK
 MD5SUM check for openjdk.tar.xz ... OK
 MD5SUM check for corba.tar.xz ... OK
 MD5SUM check for jaxp.tar.xz ... OK
 MD5SUM check for jaxws.tar.xz ... OK
 MD5SUM check for jdk.tar.xz ... OK
 MD5SUM check for langtools.tar.xz ... OK
 MD5SUM check for nashorn.tar.xz ... OK
 MD5SUM check for hotspot.tar.xz ... OK
 Building package openjdk8-8u292-x86_64-1_SBo.tgz ... OK
 Installing package openjdk8-8u292-x86_64-1_SBo.tgz ... OK

openjdk7 also built just fine as that's the requirement to build openjdk8


--
Willy Sudiarto Raharjo



Yes I noted from your earlier message you had success in a VM.

The physical machine platform I used was not so.  Strange.

I will take the hit and strip it and have another go and see what happens.

Essentially just repeating earlier what I did earlier, repartition disk 
etc, Install Slackware 15 64, update it using 'update-all' (slackpkg) 
then install gcc5, apache-ant, openjdk7, openjdk8 using the packages on 
'slackbuilds'.


Regards
Habs


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

Hello folks

Perhaps I should have mentioned in my OP, it is a clean Slackware 15 64bit 
machine, just freshly installed and fully updated on April 3rd, before 
starting the openjdk8 build (ie. installing gcc5, apache-ant openjdk7 and 
lastly openjdk8).  It baulks at openjdk7 with errors as detailed in the 
OP.


The build was tried manually  and using sbotools. Same result.

Regards
Habs



On Tue, 5 Apr 2022, Lenard Spencer wrote:


I have submitted  OpenJDK8.tar.gz to SBo.  I am also attaching a patch here
for Strahil's openjdk8 script.
As for openjdk(6,7), my scripts share a common problem when building on
32-bit.  They both fail to link with gcc5 libstdc++.so.6, insisting instead
on trying to link with /usr/lib/libstdc++.so.6, which belongs to gcc11.
Building on 64-bit doesn't show this problem.


On Mon, Apr 4, 2022 at 10:39 AM Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:


Il giorno lun 4 apr 2022 alle ore 16:29 Lenard Spencer <
lenardrspen...@gmail.com> ha scritto:


openjdk8 now also requires gcc5, and will build with zulu-openjdk7 with a
minor script edit (BOOT_JAVA to point to zulu-openjdk7).  If the maintainer
approves I can send the patch.

I also have an SBo script that builds OpenJDK8 without using icedtea,
using zulu-openjdk7 (a repackaged binary).  If there is interest I can
submit it.


On Mon, Apr 4, 2022, 09:10 Habs  wrote:


Hello everyone, good day

Slackware 15, clean, fully updated

The build either manually or via sbotools fails at the same place at the
openjdk7 part.

(part of the buildlog is below up until it bails out).

Is it something I'm doing or something in the slackbuild and associate
files and is there a quick 'fix' to try please ?

Regards
Habs



/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar

-C
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/

.
/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar

-C
/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but
got
0xc7a06d31)
 at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
 at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
 at java.io.FilterInputStream.read(FilterInputStream.java:107)
 at sun.tools.jar.Main.copy(Main.java:822)
 at sun.tools.jar.Main.update(Main.java:584)
 at sun.tools.jar.Main.run(Main.java:224)
 at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: ***
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86:

/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar]

Error 1
gmake[8]: Leaving directory

'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: ***
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64:

all] Error 2
gmake[7]: Leaving directory

'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: ***
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103:

sa_stuff] Error 2
gmake[6]: Leaving directory

'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: ***
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323:

product] Error 2
gmake[5]: Leaving directory
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'
gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'
gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2




Hi Lenard,

yes, and please have a look at openjdk7 too because here, testing the
build locally, I got the same error as Habs:

cp
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/sun/jvm/hotspot/ui/resources/*.png
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/sun/jvm/hotspot/ui/resources/
cp -r
/tmp/sbopkg.i7xegz/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes/images/*
/tmp/sbopkg.i7xegz/open

[Slackbuilds-users] openjdk8 compile (either manually or via sbotools) failing at openjdk7

[Habs]

Hello everyone, good day

Slackware 15, clean, fully updated

The build either manually or via sbotools fails at the same place at the 
openjdk7 part.


(part of the buildlog is below up until it bails out).

Is it something I'm doing or something in the slackbuild and associate 
files and is there a quick 'fix' to try please ?


Regards
Habs



/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar cf 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/saclasses/ 
.
/tmp/SBo/openjdk7/icedtea-build/bootstrap/jdk1.6.0/bin/jar uf 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar 
-C /tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/agent/src/share/classes 
META-INF/services/com.sun.jdi.connect.Connector
java.util.zip.ZipException: invalid entry CRC (expected 0x3943b2a7 but got 
0xc7a06d31)

at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:413)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:195)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at sun.tools.jar.Main.copy(Main.java:822)
at sun.tools.jar.Main.update(Main.java:584)
at sun.tools.jar.Main.run(Main.java:224)
at sun.tools.jar.Main.main(Main.java:1231)
gmake[8]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:86: 
/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product/../generated/sa-jdi.jar] 
Error 1
gmake[8]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[7]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/sa.make:64: 
all] Error 2
gmake[7]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[6]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/makefiles/top.make:103: 
sa_stuff] Error 2
gmake[6]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir/linux_amd64_compiler2/product'
gmake[5]: *** 
[/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make/linux/Makefile:323: 
product] Error 2
gmake[5]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk.build/hotspot/outputdir'

gmake[4]: *** [Makefile:203: generic_build2] Error 2
gmake[4]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'

gmake[3]: *** [Makefile:158: product] Error 2
gmake[3]: Leaving directory 
'/tmp/SBo/openjdk7/icedtea-build/openjdk/hotspot/make'

gmake[2]: *** [make/hotspot-rules.gmk:128: hotspot-build] Error 2
gmake[2]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory '/tmp/SBo/openjdk7/icedtea-build/openjdk'
make: *** [Makefile:2357: stamps/icedtea.stamp] Error 2



--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
Get a client here: https://tox.chat/clients.html

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] linphone 404 not found

[Habs]

On Sat, 1 May 2021, Willy Sudiarto Raharjo wrote:



From a month ago or so that I first mentioned to the list and yourself,
there are still [a few] '404 not found' being returned for source
packages re:linphone

e.g. from slackbuilds page:
https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz

Is it still being maintained, or is it in hand ?


Hi Habs,

It seems the maintainer is no longer active
would you mind taking over this script?



--
Willy Sudiarto Raharjo



Hello there Willy

Thank you for the info.

I am not sure that "would you mind" is the issue (it isn't). I do not 
believe I have the skills in compilation etc, being unashamedly just a 
'user' of the very much appreciated work that you and others put in to 
this project for everyone. I realise this doesn't help any.


I will, however, spend some time looking at the script maintenance process 
to see what's involved, but in the mean time, hopefully some one better 
enabled can take it on if it [linphone] is in demand*.


Regards, peace and best wishes
Habs

*(I wonder how much SIP/Linphone is used, as other messaging apps have 
somewhat taken over).


--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
https://tox.chat/

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] linphone 404 not found

[Habs]

Hello euan@

From a month ago or so that I first mentioned to the list and yourself, 
there are still [a few] '404 not found' being returned for source packages 
re:linphone


e.g. from slackbuilds page: 
https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz


Is it still being maintained, or is it in hand ?

Regards, best wishes
Habs

--- Sent using Alpine/Pine, probably the best MUA ---

My Tox Messaging Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
https://tox.chat/

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] linphone and related sources links 404 not found (fwd)

[Habs]

Hello slackbuilds-users@

There are still [a few] '404 not found' being returned for linphone and 
related package sources.


Nothing heard back from the maintainer (see below).

Regards
Habs

-- Forwarded message --
Date: Mon, 1 Feb 2021 11:41:04 + (GMT)
From: Habs 
To: slackbuilds-users@slackbuilds.org
Subject: linphone and related sources links

Hello slackbuilds-users@

Some Linphone and related source links are returning 404 (not found).

e.g.  https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz

Maintainer informed (13/1).

Sorry if this is already in hand.

Regards
Habs

--- Sent using Alpine/Pine, probably the best MUA ---

Tox Chat Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
https://tox.chat/

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] linphone and related sources links

[Habs]

Hello slackbuilds-users@

Some Linphone and related source links are returning 404 (not found).

e.g.  https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz

Maintainer informed (13/1).

Sorry if this is already in hand.

Regards
Habs

--- Sent using Alpine/Pine, probably the best MUA ---

Tox Chat Id:
9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925
https://tox.chat/

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] inkscape md5sum

[Habs]

On Sun, 19 Jul 2020, Dave Woodfall wrote:


On 19/07/20 12:06,
Habs  put forth the proposition:

Hello Fernando
Today I am compiling inkscape and the  source md5sum does not match the one
provided in the SBo info.
md5 of source gives: a6624720a925e7cc885e7df9927daffb
md5 from info: ac30f6d5747fd9c620c00dad500f414f
Thank you
Habs
--- Sent using Alpine/Pine, probably the best MUA ---


I don't think the source download link is downloading the source.  Try
this:

https://inkscape.org/gallery/item/13330/inkscape-0.92.4.tar.bz2

You will need to remove the $PRGSUB part of the tar command line in
the slackbuild for it to work though.

--
Dave



Thank you for the link.  I do not know what has gone on there with that 
SBo build package, or why the PRGSUB addition etc. I will try compile it 
later.


Regards
Habs

--- Sent using Alpine/Pine, probably the best MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] inkscape md5sum

[Habs]

Hello Fernando

Today I am compiling inkscape and the  source md5sum does not match the 
one provided in the SBo info.


md5 of source gives: a6624720a925e7cc885e7df9927daffb

md5 from info: ac30f6d5747fd9c620c00dad500f414f


Thank you
Habs

--- Sent using Alpine/Pine, probably the best MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Download Lyx source code issues

[Habs]

Good day rsamurti  (cc: slackbuild-users)

I am struggling to download the "Lyx" source code - there is no access and it 
seems as if the source location has moved/changed.


Even going to the Lyx website and trying from there is causing issues...it 
seems upstream have changed things...or is it just me !


Regards
Habs

PS: reposted this original as missing 'subject' on previous - apologies.

--- Sent using Alpine/Pine, a text based MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] (no subject)

[Habs]

Good day rsamurti  (cc: slackbuild-users)

I am struggling to download the "Lyx" source code - there is no access and 
it seems as if the source location has moved/changed.


Even going to the Lyx website and trying from there is causing issues...it 
seems upstream have changed things...or is it just me !


Regards
Habs

--- Sent using Alpine/Pine, a text based MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Updates - 20181209.1

[Habs]

On Sun, 9 Dec 2018, Willy Sudiarto Raharjo wrote:


Hi,

Sorry for the delay, but last minute submission requires big deps (Qt5,
webkitgtk, and opencv), so compiling them take some time along with our
busy schedule in our daily life.




Thank you.

As far as I am concerned, there is no need to ever feel a need to 
apologise on matters like this.  It is appreciated very much what effort 
goes in to making all this available to everyone.


--- Sent using Alpine/Pine, a text based MUA ---
Tox-id:
96945E2B98A02A58E86B08D104B9B9DBDC9C9CBAC04D8E96274AAC62CC50747FCB281137C07A
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] MD5 hash sums

[Habs]

On Thu, 23 Aug 2018, Erik Hanson wrote:

On 8/23/18 5:59 PM, t...@airmail.cc wrote:


So, one can verify the authenticity of the SlackBuild script, but the
authenticity of the source tarball itself used by the aforementioned
script is uncertain? If that's the case then why would one bother with
verifying authenticity at all? (Something authentic) x (Something that
may or may not be authentic) == (Something that may or may not be
authentic), right?


It's been mentioned in this thread enough times that MD5 has not fallen
to the attack you think it has, so I won't repeat that talking point,
but I will try and clarify something..

The checksums are not there to verify authenticity. Everyone seems to be
putting far too much stock in the MD5 sums in the .info files. I can't
stress this enough: they're not there for security.

You could almost think of it as a version number. If the file you
download matches the MD5 sum provided, then you know it's the same file
the maintainer used, and the same file the SlackBuild was tested against
by a SlackBuilds.org admin. This helps to ensure the SlackBuild will
work as intended, creating a valid package.

What the MD5 sum can, and does do on a regular basis, is raise a red
flag when it mismatches. Possibly the source has gone missing, or been
replaced by upstream without a change to the file name. These things
happen often enough that it's important we have a checksum, and that
people use it rather than complain that a SlackBuild is broken.

However, you absolutely cannot assume that because the MD5 sum matches
that the file is in any way "safe" or was not tampered with /before/ the
maintainer got to it. Auditing or policing upstream sources is far
beyond the scope of this project. We could use the strongest hashing
algorithm available, but telling people it's a mark of authenticity
would be nothing but theater.


--
Erik




It seems clear enough to me and has done since it was explained to me a
while back.

Effectively, if the maintainer unfortunately has used an 'unsafe' source, 
created its checksum for that source and then uploaded the build package, 
then all the checksum is doing when use it, is validating it was that 
original unsafe source (assuming it hasn't again been altered); or more 
preferably and likely the 'safe' source - as said, there is nothing SBo 
can do about unsafe sources and updating to better checksums etc won't 
help that it seems to me.


I think the current approach is 'safe enough' once one accepts the above
to prove nothing was tampered with when we get it - or at least will let
us know.

I stand to be corrected, however.

Habs

--- Sent using Alpine/Pine, a text based MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] [OT] Screen grabber ?

[Habs]

On Wed, 4 Jul 2018, Xavier Maillard wrote:


Date: Tue, 26 Jun 2018 18:35:59 +0200 (CEST)
From: Kees Theunissen 

I always use "xv" (included in slackware since a very long time).

Start xv, right-click on the xv window and click the "Grab"
button from the "xv controls" pop up.


Thank you but as said, I am into a linux console aka. the thing right
after the linux kernel has started with the "login:" prompt.

I have no X running here (not yet at least).
--
Xavier Maillard
e/j:xav...@maillard.imw:www.maillard.im
m: 06 52 18 63 43

GPG:   9983 DCA1 1FAC 8DA7 653A
  F9AA BA49 09B7 8F04 DE1B
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




A quick search threw up this;  is this any help:

http://www.pc-freak.net/blog/how-to-make-screenshot-in-devtty-console-on-gnu-linux-taking-picture-jpeg-png-snapshot-of-text-console-in-systems-without-graphical-environment/


or

'fbcat' on slackbuilds  maybe

regards
H.


--- Sent using Alpine/Pine, a text based MUA ---
Tox-id:
96945E2B98A02A58E86B08D104B9B9DBDC9C9CBAC04D8E96274AAC62CC50747FCB281137C07A
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Build failure: gnucash 2.6.19

[Habs]

On Sun, 1 Apr 2018, David O'Shaughnessy wrote:


I'm having trouble building the latest gnucash 2.6.19. The last bit of
error output is:


libtool: link: gcc -Wdeclaration-after-statement -Wno-pointer-sign 
-D_FORTIFY_SOURCE=2 -O2 -fPIC -std=gnu99 -Wall -Wunused -Wmissing-prototypes 
-Wmissing-declarations -Wno-unused -o .libs/gnucash gnucash-bin.o -pthread 
-Wl,--export-dynamic -pthread  
../../src/register/ledger-core/.libs/libgncmod-ledger-core.so 
../../src/report/report-gnome/.libs/libgncmod-report-gnome.so 
../../src/gnome/.libs/libgnc-gnome.so 
../../src/gnome-utils/.libs/libgncmod-gnome-utils.so 
../../src/app-utils/.libs/libgncmod-app-utils.so 
../../src/engine/.libs/libgncmod-engine.so 
../../src/gnc-module/.libs/libgnc-module.so 
../../src/core-utils/.libs/libgnc-core-utils.so 
../../src/libqof/qof/.libs/libgnc-qof.so 
../../src/report/report-system/.libs/libgncmod-report-system.so 
/usr/lib64/libguile-2.0.so /usr/lib64/libgc.so /usr/lib64/libgthread-2.0.so 
/usr/lib64/libgmodule-2.0.so /usr/lib64/libgtk-x11-2.0.so 
/usr/lib64/libgdk-x11-2.0.so /usr/lib64/libpangocairo-1.0.so 
/usr/lib64/libatk-1.0.so /usr/lib64/libcairo.s

o

 /usr/lib64/libgdk_pixbuf-2.0.so /usr/lib64/libgio-2.0.so 
/usr/lib64/libpangoft2-1.0.so /usr/lib64/libpango-1.0.so 
/usr/lib64/libgobject-2.0.so /usr/lib64/libglib-2.0.so 
/usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread -Wl,-rpath 
-Wl,/usr/lib64/gnucash

../../src/register/ledger-core/.libs/libgncmod-ledger-core.so: undefined 
reference to `gnc_recn_cell_set_read_only'
collect2: error: ld returned 1 exit status

[cut]

I'm building in a proper root shell (with 'su -') and have tried
recompiling all the dependencies, but that doesn't help. Any clues?

--
Dave
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/




I can confirm the same error while trying to build with [a previous 
version] gnucash installed.


The build completes with gnucash removed before building, as has been 
mentioned in another followup (thanks for reminding).


Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Today's DMARC debacle

[Habs]

Hello List, Rob McGee

On Wed, 21 Mar 2018, Rob McGee wrote:


Some of you might not have seen this because your list delivery was
suspended.  We think we have all the subscribers reenabled now.

The "fix" has been implemented and confirmed to work.  "Fix" is the
wrong word; it is a workaround for the shortcomings of the DMARC
protocol.  Our list was fine, but we had to break it in case some
other poster gets the same silly idea to play with DMARC.




Does DMARC have to be specifically setup by a domain admin ? i.e. it can't 
just be inadvertently turned on.


I presume it does based on what I read briefly, about adding entries into 
the domain records etc. I have to admit until I read about it on this list 
I was almost fully clueless as to what DMARC was (acronyms to the ignorant 
and all that).


Habs

--- Sent using Alpine/Pine MUA ---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] qt5 build failed

[Habs]

Hello List, Larry


I had a go at building qt5 (slackware fully updated 14.2 64b) and when
using the DOCS=yes EXAMPLES=yes setting, the build failed

.
.
.
make[4]: Leaving directory
'/tmp/SBo/qt-everywhere-opensource-src-5.7.1/qtcharts/examples'
make[3]: Leaving directory
'/tmp/SBo/qt-everywhere-opensource-src-5.7.1/qtcharts' make[2]: Leaving
directory '/tmp/SBo/qt-everywhere-opensource-src-5.7.1' Makefile:1086:
recipe for target 'html_docs' failed make[1]: *** [html_docs] Error 2
make[1]: Leaving directory
'/tmp/SBo/qt-everywhere-opensource-src-5.7.1' Makefile:1089: recipe for
target 'docs' failed make: *** [docs] Error 2



Leaving out the DOCS=yes EXAMPLES=yes setting, it built fine, so I do
have a build at least.

I haven't noticed if anyone else has had the same problem, so I
thought I'd mention it.


Cheers for eveyone's continuing hard work in contributions and
maintenance on SBo.


Habs






___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Mail archives seem to be unavailable

[Habs]

On Sun, 24 Sep 2017 07:32:54 -0500
Rob McGee  wrote:

> 
> Yep, thanks for the notice.  For some reason yet unknown, httpd 
> wasn't running.  It's started now, and IWFM.


i know im not young anymore...but what is IWFM.

i had to look it up!   im going for  'it works for me' ?

;-)

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Tue, 19 Sep 2017 13:17:30 +0200
Andrzej Telszewski <atelszew...@gmail.com> wrote:

> Hi,
> 
> I've just built for testing (I don't need the package) with slackrepo:
> 
> env MAKEFLAGS=' -j4 ' nice -n 5 bash ./webkit2gtk.SlackBuild
> Build time 187 min, peak load 6.69, peak memory 3674M, peak tmp 1222M
> Built ok:  webkit2gtk-2.18.0-x86_64-1_sbo.txz
> 


That did the trick. \m/ Before messing with swap, I tried this first and
the machine romped through it with no [resource] issues that I could
see. Thank you for this ... and to all for the other contributions.

I've realised I know very little comparatively :-)

Regards
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Tue, 19 Sep 2017 10:56:16 +0200
Matteo Bernardini <matteo.bernard...@gmail.com> wrote:

> 2017-09-18 21:52 GMT+02:00 Habs <gen-...@useyouresp.org.uk>:
> > From reading other posts, I will have a go with the -j switch and
> > see what gives, but it seems remote.  Not sure what else to do, or
> > I can do.  The previous version builds fine, so I can use that and
> > not upgrade any more, until I understand what's going on (hmmm).  
> 
> I was able to reproduce your error when building webkit2gtk with a
> single make job (the default), while it went fine if two jobs or more
> were used.
> 
> you can try adding a line like this to the SlackBuild (so that it
> defaults to use at least two jobs)
> 
> --- webkit2gtk.SlackBuild.orig  2017-09-16 02:20:30.0 +0200
> +++ webkit2gtk.SlackBuild   2017-09-19 10:54:00.493180645 +0200
> @@ -55,6 +55,8 @@
>LIBDIRSUFFIX=""
>  fi
> 
> +MAKEFLAGS=${MAKEFLAGS:--j2}
> +
>  set -eu
> 
>  rm -rf $PKG
> 
> or you can try also passing a MAKEFLAGS=-j${n} (with n >= 2) to the
> SlackBuild to use multiple make jobs.
> 
> Matteo
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

Thank you will give a few things a try until it builds or I give up due
to lack of brain capacity (and frustration)   :-)
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Tue, 19 Sep 2017 10:44:02 +0700
Willy Sudiarto Raharjo <will...@slackbuilds.org> wrote:

> On 09/19/2017 04:49 AM, Jason Graham wrote:
> > On Mon, Sep 18, 2017 at 12:20 PM, Habs <gen-...@useyouresp.org.uk>
> > wrote: 
> >>
> >> Ive started the build off again after clearing it out.
> >> As I said, I'm simple minded ;-)  so please forgive me, but it
> >> puzzles me that the error message is related to space - is that
> >> disk resource and,or ram resources  ...and more over, why would
> >> the previous version build fine on the exact same machine _without
> >> issue_ but not this updated version...what is it doing different I
> >> wonder (all said rhetorically speaking).
> >>
> >>  
> > The missing header file issue between the two -j values is indeed a
> > bit baffling (if it were happening with anything other than -j1
> > that would seem to make more sense).
> > 
> > With regard to the resource requirements for the build, passing
> > -DCMAKE_VERBOSE_MAKEFILE=1 will show how involved building this
> > package is. There are at least 100 different include directories
> > used during compilation of each file so header files are scattered
> > all throughout the source tree. I'd say a similar number of object
> > files for each library it creates during linking which seem to be
> > the most demanding with regard to memory.  
> 
> Just a short FYI that i'm able to build webkit2gtk on my
> Slackware64-14.2 VM with 1 vCPU and 2 GB of RAM with 10 additional
> swap space (total of 12 GB) using commands that Ponce stated in LQ
> thread
> 
> fallocate -l 10G /temp-swap
> chmod 0600 /temp-swap
> mkswap /temp-swap
> swapon /temp-swap
> 
> webkit2gtk:
>   MD5SUM check for webkitgtk-2.18.0.tar.xz ... OK
>   Building package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK
>   Installing package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK
> 
> free -h
>   totalusedfreeshared  buff/cache   available
> Mem:  1.9G 22M 123M4K1.8G1.6G
> Swap: 12G  22M 12G
> 
> 

Can I just have clarified please re:

> fallocate -l 10G /temp-swap
> chmod 0600 /temp-swap
> mkswap /temp-swap
> swapon /temp-swap

... that be done without messing up the swap already setup (in fstab)
i.e. it is a temporary allocation for the build process that can then
be deallocated etc  (hopefully you get what I mean) ?

The machine I'm using already has 8b swap (I believe) and 4Gb RAM.
I will track down the thread on LQ and try it out...but it is getting a
bit silly when a 4GB quad-core machine that is doing nothing else,
struggles or conks out due to resource issues etc :-)


Thank you again all for the input...maybe I am learning something too!

Habs




___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Mon, 18 Sep 2017 17:20:21 +0100
Habs <gen-...@useyouresp.org.uk> wrote:

> On Mon, 18 Sep 2017 11:02:48 -0400
> Jason Graham <jgra...@gmail.com> wrote:
> 
> > On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha <y...@ythogtha.org> wrote:
> >   
> > > > > I got the same error as Habs on a stable install.
> > > >
> > > > I was convinced by Matteo and David that webkit2gtk build fine
> > > > on stable and current for both arch, BUT it requires a LOT of
> > > > resources, so i cancelled my revert and update README instead to
> > > > make additional SWAP space if you have small amount of memory
> > > > installed.
> > >
> > > After the package is created, the temporary build
> > > directory takes 1.1Gb.
> > > It's not that big, but it is also true that the build takes up a
> > > lot of resources during compilation.
> > > My computer only has 8Gb of RAM. Maybe using multiple jobs
> > > may be a problem, I use -j2, and my computer is on its knees (or
> > > chips, or circuits, don't know... ^^) when building, but it builds
> > > fine.
> > >
> > >
> > >
> > 
> > I had a similar experience. I first tried with -j8 on a VM and the
> > compilation finished (or at least the cmake progress showed 100%)
> > but it didn't proceed from there. There were 4Gb of ram allocated
> > to this VM so I suppose it was resource constrained based on other
> > folks' findings. It stalled for quite some time (~30min) before I
> > killed the job.
> > 
> > So I tried again with -j1 and it failed in the same location has
> > Habs.
> > 
> > Best,
> > Jason  
> 
> Ive started the build off again after clearing it out.
> As I said, I'm simple minded ;-)  so please forgive me, but it puzzles
> me that the error message is related to space - is that disk resource
> and,or ram resources  ...and more over, why would the previous version
> build fine on the exact same machine _without issue_ but not this
> updated version...what is it doing different I wonder (all said
> rhetorically speaking).
> 
> I will see what happens in the early hours  :-)
> 
> Thanks again everyone
> Habs

Well, it failed again - both machines (one Intel one AMD tower) - as
detailed previously.  They were doing nothing else other than building
this.

The machines are by no means gutsy, but still...4Gb RAM, 500Gb disk
space etc. Swap wasnt overly affected from what I could see, which
just leaves memory etc ...why would that cause it to conk I dunno.

If it is  a resources issue for building, producing the error at the
same place each time, then it seems like its getting to the point of
needing a Cray computer to do this. Ridiculous.  :-)

>From reading other posts, I will have a go with the -j switch and see
what gives, but it seems remote.  Not sure what else to do, or I can
do.  The previous version builds fine, so I can use that and not
upgrade any more, until I understand what's going on (hmmm).

Thank you, good night (as it is for me) to all.
Habs

---
[ 76%] Building CXX object
Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o
In file included
from 
/tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0:
/tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40:
fatal error: WebCore/HysteresisActivity.h: No such file or directory
compilation terminated.
Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for
target
'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o'
 failed
make[2]: ***
[Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o]
Error 1
CMakeFiles/Makefile2:1065: recipe for target
'Source/WebCore/CMakeFiles/WebCore.dir/all' failed
make[1]: *** [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2

---
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Mon, 18 Sep 2017 11:02:48 -0400
Jason Graham <jgra...@gmail.com> wrote:

> On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha <y...@ythogtha.org> wrote:
> 
> > > > I got the same error as Habs on a stable install.  
> > >
> > > I was convinced by Matteo and David that webkit2gtk build fine on
> > > stable and current for both arch, BUT it requires a LOT of
> > > resources, so i cancelled my revert and update README instead to
> > > make additional SWAP space if you have small amount of memory
> > > installed.  
> >
> > After the package is created, the temporary build directory
> > takes 1.1Gb.
> > It's not that big, but it is also true that the build takes up a
> > lot of resources during compilation.
> > My computer only has 8Gb of RAM. Maybe using multiple jobs
> > may be a problem, I use -j2, and my computer is on its knees (or
> > chips, or circuits, don't know... ^^) when building, but it builds
> > fine.
> >
> >
> >  
> 
> I had a similar experience. I first tried with -j8 on a VM and the
> compilation finished (or at least the cmake progress showed 100%) but
> it didn't proceed from there. There were 4Gb of ram allocated to this
> VM so I suppose it was resource constrained based on other folks'
> findings. It stalled for quite some time (~30min) before I killed the
> job.
> 
> So I tried again with -j1 and it failed in the same location has Habs.
> 
> Best,
> Jason

Ive started the build off again after clearing it out.
As I said, I'm simple minded ;-)  so please forgive me, but it puzzles
me that the error message is related to space - is that disk resource
and,or ram resources  ...and more over, why would the previous version
build fine on the exact same machine _without issue_ but not this
updated version...what is it doing different I wonder (all said
rhetorically speaking).

I will see what happens in the early hours  :-)

Thanks again everyone
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] webkit2gtk build problems

[Habs]

On Mon, 18 Sep 2017 11:59:02 +0200
Ythogtha <y...@ythogtha.org> wrote:


> > Hi
> > 
> > I think i made a mistake when testing this build. I *may have* ran
> > it on a current VM rather than a stable VM, so i'm reverting it to
> > 2.16.0 in my branch for now while i'm investigating it further.
> > 
> > 
> > -- 
> > Willy Sudiarto Raharjo
> >   
> 
>   I've just compiled it fine on a slackware64 14.2 fully
> patched, but with a lot of other packages in it, so not a clean
> install, but still not on a current branch. I didn't rebuild any
> dependency since my last 2.16 build, compilation was already ongoing
> when you sent your message, and I just let it go to see what would
> happen.
> 
>   Are you sure you didn't ran out of disk space ? It's taking a
> lot of it during compilation
> 

Hard disk space, no I dont think it is a partition space issue on the
machine how much would it require with this release compared to
previous ?

The error message I attached, could that be caused by space issues?

Thank you
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] webkit2gtk build problems

[Habs]

Hello All

I'm afraid, I need some help please to sort out what's going on with
the build for webkit2gtk (2.18.0) downloaded via SBo today onto 
slackware 14.2 64bit full standard install.

I have run the build on two different machines (AMD and Intel) and both
coming back with same error at same place. Previous version build fine.




Do I need to rebuild the listed dependencies (actually on the Intel all
were built), or is it something else that you can spot for me please ?

Not sure, but I wonder if I've missed previous posts about
this..perhaps not ...  my mind is a sieve.

(build error attached below).

Thank you for any ideas/help etc.

Habs

[ 76%] Building CXX object
Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o
In file included
from 
/tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0:
 
/tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40:
fatal error: WebCore/HysteresisActivity.h: No such file or directory
compilation terminated.
Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for
target
'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o'
failed make[2]: ***
[Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o]
Error 1 CMakeFiles/Makefile2:1065: recipe for target
'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: ***
[Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149:
recipe for target 'all' failed make: *** [all] Error 2 r
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Very simple way of finding dependency

[Habs]

On Wed, 13 Sep 2017 16:06:54 +0100
David Spencer <baildon.resea...@googlemail.com> wrote:

> Chris Willing's tool hoorex will find "inverse dependencies" of
> packages. https://github.com/cwilling/hoorex
> 
> One other idea for finding why you installed a library -- you can list
> the files in /var/log/packages sorted by time (ls -lt) which will show
> you the other packages that were installed immediately afterwards.
> 
> Twenty years ago I wrote this kind of thing in a little book. Ten
> years ago I used dokuwiki. Now I just never uninstall them.
> 
> There is no official test build system that would have a full listing
> of files. Unofficially, I build almost every package from time to
> time. A list of files (depending on random options) in almost every
> package is 325 Mb. I'm not sure I would want to put them unofficially
> on a website somewhere if each query will grep 325Mb of data. (And
> also I hate elasticsearch.)
> 


Im likely comparatively poor at sysadmin, but my approach re:slackware
taken from my old school a long time is to create (and try to maintain
haha) a register of any software added afterwards...inc documenting the
dependencies etc.

Its only a simple xml affair that records whats listed on SBo as
required and optional (if ive intalled the optional stuff) etc, but i
can cross check stuff easily enough.

My biggest problem is laziness in keeping up to it :-)

Of course this is all no good, if its not done right from the get go.

As mentioned above though, I find the var/log/packages thing can get me
some way.

I like Slackware and SBo - I think the community is great and thanks to
everyone involved keeping it ie. Slackware and SBo, as it is. If it went
full-on like the other distros, it would be a shame.

Have a lovely day folks. Peace best wishes

Habs

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Advice needed: no libpng14.la

[Habs]

On Mon, 21 Aug 2017 19:07:30 +0200
Didier Spaier <did...@slint.fr> wrote:

Sorry for the general chit-chat type thing here from me and apologies
about not specifically related to libpng, but this caught my eye and I
couldn't help but muse about it...

> 
> I don't have the answer, but will take this opportunity for a warning
> to users of packages depending on webkitgtk2, directly or indirectly.
> 
> Having read this blog post:
> https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/
> 
> I assume that all software that depend on a version at risk according
> to the most recent security advisory published on
> https://webkitgtk.org/security.html
> are also at risk.
> 
> Today that would mean that version 2.16.6 should be used instead
> of 2.4.11 (the default in SBo).
> 
> Admittedly the risk level is not the same for all software that depend
> on webkitgtk2, as explained by  Michael Catanzaro, and maybe one


I think its time for me to retire...this did my head in ;-)

from the blog link above (no criticism of the author):
".. WebKit2 has been around for Mac and iOS for longer, but the first
stable release for WebKitGTK+ was the appropriately-versioned
WebKitGTK+ 2.0, in March 2013. This release actually contained three
different APIs: webkitgtk-1.0, webkitgtk-3.0, and webkit2gtk-3.0.
webkitgtk-1.0 was the original API, used by GTK+ 2 applications.
webkitgtk-3.0 was the same thing for GTK+ 3 applications, and
webkit2gtk-3.0 was the new WebKit2 API, available only for GTK+ 3
applications..."


So on SBo there are 3 'webkits':  webkitgtk  webkit2gtk and
webkitgtk3.  There are only a few apps that use webkitgtk I believe -
at least that I use (e.g. gnucash).

As an aside, I thought Midori uses webkitgtk3 (by specific enable).

Any way,  are any of these 'safe' having read this without regular
update. I have for a while been of the belief that webkitgtk should not
be used - and webkit2gtk used instead and webkitgtk3 if poss.  I have
never been too sure why.

It takes an age to compile webkit (any of them) unless blessed with
some processing power and even then I can imagine it takes a while.

It is the sort of thing where by if there were a trusted resource
lastest release type thind - precompiled - I might use it.  So far I
still compile.

I cant help feeling Webkit is a [polite] mess! :-)  An although that
blog piece is a year ago or so,  has anything changed I wonder.

Perhaps I am being too paranoid - but it did make me take notice.


Habs






___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] http://www.hyperrealm.com/libconfig/

[Habs]

Hello good morning all

Server error @ http://www.hyperrealm.com/libconfig/

libconfig-1.5.tar.gz


Is there an alternative link for now please ?


Thanks
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] icecat 52.1.0 build error

[Habs]

On Thu, 1 Jun 2017 15:45:24 +0700
Willy Sudiarto Raharjo  wrote:

> > Hi - excellent, thank youwhat was the 'fix' please ?  
> > 
> > (apologies, i am not familiar with branches etc yet, to go check
> > there...i just use the website)  
> 
> Probably it's easier to see it here:
> https://slackbuilds.org/ready/
> 
> you can click on the commit ID to get you to the real commit
> 
> 

thank you - bookmarked! :-)  have a nice day all.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] icecat 52.1.0 build error

[Habs]

On Thu, 1 Jun 2017 15:32:51 +0700
Willy Sudiarto Raharjo  wrote:

> > Hello melikamp, good morning to all
> > 
> > I have just tried the icecat build and it quit after the following
> > message:
> > .
> > icecat/platform.ini
> > cp: cannot stat '[...]/icecat/Changelog.*': No
> > such file or directory
> > 
> > It seems to be because of a 'cp' of $CWD/README* and
> > $CWD/Changelog.*, where there is no Changelog.* in the CWD.
> > 
> > As a test, I removed the Changelog.* part and it was ok.  Is that
> > bit significant, or just an artifact from your setup ?  
> 
> It has been fixed on my branch few hours ago
> 
> 

Hi - excellent, thank youwhat was the 'fix' please ?  

(apologies, i am not familiar with branches etc yet, to go check
there...i just use the website)
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] icecat 52.1.0 build error

[Habs]

Hello melikamp, good morning to all

I have just tried the icecat build and it quit after the following
message:

.
.
.
icecat/platform.ini
cp: cannot stat '[...]/icecat/Changelog.*': No
such file or directory



It seems to be because of a 'cp' of $CWD/README* and $CWD/Changelog.*,
where there is no Changelog.* in the CWD.

As a test, I removed the Changelog.* part and it was ok.  Is that bit
significant, or just an artifact from your setup ?


Thank you
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Flowblade

[Habs]

Hi there Klaatu

Thank you for replying.

> I don't personally like to rush into updates on stable software. 

Yes I agree with you.


My request was driven out of an annoying thing I couldnt find a
solution for.

The 'render with args' check and edit boxes do not show up on 'small
screens' and it seems there is no config item to get FB to switch off
'small screen checking' and so [hopefully] display the render args
sections. There's a few posts, but it came down to updating being a
better solution with the other things changed since the 1.6.

The later builds have allegedly fixed the issue.

Any way, I realise there is a fair bit of work, checking and
testing, so thank you for considering and I will be pleased when you
get some time to have a look.

Cheers
Keep well
Habs




On Wed, 03 May 2017 05:39:04 +1200
kla...@mixedsignals.ml wrote:

> Hi Habs,
> 
> I can update FlowBlade, but if your build is going well, it's
> probably just as good as whatever I'll post. You can start editing
> with what you've got.
> 
> I don't personally like to rush into updates on stable software. I'll
> do some testing of the latest FlowBlade and update the build assuming 
> nothing crashes and burns horribly.
> 
> I'd love to hear other maintainer's input about checksums from
> github. To my knowledge, there are none from Github upstream unless
> the developer goes out of their way to post them somewhere. For SBo,
> I just generate an md5sum based on what I've downloaded and put that
> into .info. Not great, I know, but at least it's a fingerprint.
> 
> -klaatu
> 
> 
> 
> 
> On 2017-05-03 04:08, General wrote:
> > FAO Maintainer (cc'd slackbuilds-users)  Klaatu
> > 
> > Flowblade is several releases on now (1.12 ?). With respect to the 
> > effort
> > involved, I was wondering if 'we' might be seeing an update to the 
> > latest
> > version soon please?
> > 
> > I've had a go a running the build script against 1.10 and it seemed
> > to go
> > ok, but I'm never too sure ;-)
> > 
> > Which leads me to another [general] question:  when getting a
> > source of Github (of which I am not too familiar) , what happens in
> > terms of process
> > that leads to the md5sum's on the slackbuilds.org. I could not
> > see any
> > published [by the developers] any checksums etc ?
> > 
> > Keep up the good work everyone. It does not get said enough
> > probably, but
> > the time and effort that contributors and maintainers etc put in to 
> > this
> > SlackBuilds project (and quality open source in general) is most
> > appreciated. Thank you.
> > 
> > 
> > Habs  

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] md5sums [was: Flowblade]

[Habs]

On Tue, 2 May 2017 12:28:46 -0400
B Watson <yalh...@gmail.com> wrote:

> On 5/2/17, General <gen-...@useyouresp.org.uk> wrote:
> >
> > Which leads me to another [general] question:  when getting a
> > source of Github (of which I am not too familiar) , what happens in
> > terms of process that leads to the md5sum's on the
> > slackbuilds.org. I could not see any published [by the
> > developers] any checksums etc ?  
> 
> Whoever writes the SlackBuild downloads the file and calculates its
> md5sum. In other words, they come from the SBo maintainer, not from
> the upstream devs.
> 
> As a user, the md5sum matching means you're using the same source as
> the SBo maintainer wrote his script for... but there's no 'chain of
> trust' beyond that.
> 
> (About now, someone will chime in with 'But md5 is weak and has been
> exploited!', I'll leave that discussion for later...)
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


Thank you for the reply.  Ahh I see.  I had it in my mind that
upstream/devs would post a [sourse] release as such with some checksum,
so that when it arrived elsewhere it could be validated (as best one
can) to not have been meddled with.

Cheers.
Habs
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/