SBo scripts not building on current (read 1st post, pls)

hendrickxm · 11-12-2016, 12:23 PM

Quote:

Originally Posted by orbea

scons is now included in Slackware-14.2.

http://packages.slackware.com/?r=sla...4.1-i586-1.txz

My mistake. I am running Salix.

sombragris · 11-12-2016, 02:34 PM

This is an ancillary issue but I think is relevant. While hunting for an odd behavior in my box, I realized that I had some perl SBo modules from the 14.1 era which were retired in 14.2:

https://lists.slackbuilds.org/piperm...er/017346.html

These modules were removed because 14.2 Perl already included them so these were redundant.

The problem is that there was no such mention of the removal in the SBo ChangeLog *or* Slackware ChangeLog *or* CHANGES_AND_HINTS.TXT. The only way to realize about their removal was, as @wilysr pointed out, to look into git history:

https://lists.slackbuilds.org/piperm...er/017346.html

I submit that this is not clear not obvious, and it is not documented in any way as a way to properly follow and maintain changes in SBo. So I would request that whenever a new Slack version is released, the SBo ChangeLog could state the redundant packages without the need to resort to these methods. I don't know how to handle git; I'm just a regular user with no coding knowledge and this is not clear for me in any way.

Anyway, it's just a proposal. Thanks for bearing with me.

willysr · 11-12-2016, 06:54 PM

Hi

For perl packages, it's always a good idea to rebuilt everything on a new version of Slackware. The changes were too big and we have to check perldoc for every perl releases between 14.1 and 14.2. Even then, we still missed some packages and remove it later after the 14.2 repository has been opened for public. But it was a good suggestion. Let's see if we can list them and post it on the slackbuilds-users mailing list instead of the changelog for the next release.

As for git, we stopped accepting submission around January and 14.2 gets released in July. In that 6 months, there are like more than 2800+ commits in the git repository. When a new repository is released, we import them all from master to a new branch so no changelog is given except for the announcement.

USUARIONUEVO · 11-12-2016, 09:12 PM

Hi , is not a problem , but i suggest a change in winusb

Dependencies say "wxpython" , but can go with wxGTK3 , if apply that patch

https://build.opensuse.org/package/v...patch?expand=1

willysr · 11-12-2016, 10:41 PM

Is there a strong reason to change the deps from wxPython to wxGTK3?
does it fix a bug or just cosmetic?

sombragris · 11-12-2016, 11:03 PM

@wilysr: thanks for understanding.

As for perl, you are right. My box's odd behavior was due to some old perl modules. Upon a rebuilding, everything went smooth.

As for the removed packages, I think your idea is very good. The point is, as you guessed, not necessarily to include these in the ChangeLog, but just to have a more visible way to learn about these removals than seeking some git history which would not be easy to get by non-coders. This would benefit not only -current users, but also stock 14.2 users who upgraded from 14.1 and followed UPGRADE.TXT and CHANGES_AND_HINTS.TXT at the time of the release. Thanks again!!

willysr · 11-13-2016, 12:48 AM

Quote:

Originally Posted by sombragris

As for the removed packages, I think your idea is very good. The point is, as you guessed, not necessarily to include these in the ChangeLog, but just to have a more visible way to learn about these removals than seeking some git history which would not be easy to get by non-coders. This would benefit not only -current users, but also stock 14.2 users who upgraded from 14.1 and followed UPGRADE.TXT and CHANGES_AND_HINTS.TXT at the time of the release. Thanks again!!

I have started to make some notes about changes from 5.22.2 to 5.24.0 and hopefully it will be updated periodically once a new perl gets released and included in -current.

franzen · 11-13-2016, 03:39 AM

Quote:

Originally Posted by willysr

I have started to make some notes about changes from 5.22.2 to 5.24.0 and hopefully it will be updated periodically once a new perl gets released and included in -current.

Maybe some script could automatically create a txt-file from SBo-git-log on every public update,
containing

Code:

Since slackware 14.2 was released, following builds were
-added:
 packagex
 packagey

-removed:
 packagea
 packageb

, containing also some static info about special cases like the perl-upgrade issues discussed here,
and then be put on the SBo-website.

willysr · 11-13-2016, 07:06 AM

Quote:

Originally Posted by franzen

Maybe some script could automatically create a txt-file from SBo-git-log on every public update,
containing

Code:

Since slackware 14.2 was released, following builds were
-added:
 packagex
 packagey

-removed:
 packagea
 packageb

, containing also some static info about special cases like the perl-upgrade issues discussed here,
and then be put on the SBo-website.

I think this kind of request should be sent to the list instead of LQ.

USUARIONUEVO · 11-13-2016, 04:18 PM

Hi , im not sure , because i have some slakcbuilds packages, but

slackware64-14.2 + updates

openjdk --> compiled fine
openjdk8 --> error

last 10 lines when try to compile

Quote:

/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk.build-boot/jdk/objs/libverify/check_code.o: In function `verify_method':
/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk-boot/jdk/src/share/native/common/check_code.c:1033: undefined reference to `JVM_IsVMGeneratedMethodIx'
collect2: error: ld returned 1 exit status
lib/CoreLibraries.gmk:91: recipe for target '/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk.build-boot/jdk/lib/amd64/libverify.so' failed
gmake[3]: *** [/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk.build-boot/jdk/lib/amd64/libverify.so] Error 1
gmake[3]: *** Waiting for unfinished jobs....
gmake[3]: Leaving directory '/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk-boot/jdk/make'
BuildJdk.gmk:70: recipe for target 'libs-only' failed
gmake[2]: *** [libs-only] Error 2
gmake[2]: Leaving directory '/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk-boot/jdk/make'
/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk-boot//make/Main.gmk:115: fallo en las instrucciones para el objetivo 'jdk-only'
gmake[1]: *** [jdk-only] Error 2
gmake[1]: se sale del directorio '/usr/src/slapt-src/development/openjdk8/openjdk8/icedtea-build/openjdk.build-boot'
Makefile:2479: fallo en las instrucciones para el objetivo 'stamps/icedtea-boot.stamp'
make: *** [stamps/icedtea-boot.stamp] Error 2
sh openjdk8.SlackBuild Error

willysr · 11-13-2016, 07:03 PM

my first guess reading your error message is probably a race condition
i'm still building in VM, but to start with, you can try to limit the number of CPUs being used to compile OpenJDK8

willysr · 11-14-2016, 12:41 AM

I am able to build openjdk8 without issue here using sbopkg

Code:

apache-ant:
  MD5SUM check for apache-ant-1.9.7-bin.tar.bz2 ... OK
  Building package apache-ant-1.9.7-noarch-2_SBo.tgz ... OK
  Installing package apache-ant-1.9.7-noarch-2_SBo.tgz ... OK

openjdk:
  MD5SUM check for icedtea-2.6.7.tar.xz ... OK
  MD5SUM check for openjdk.tar.bz2 ... OK
  MD5SUM check for corba.tar.bz2 ... OK
  MD5SUM check for jaxp.tar.bz2 ... OK
  MD5SUM check for jaxws.tar.bz2 ... OK
  MD5SUM check for jdk.tar.bz2 ... OK
  MD5SUM check for langtools.tar.bz2 ... OK
  MD5SUM check for hotspot.tar.bz2 ... OK
  Building package openjdk-7u111b01-x86_64-1_SBo.tgz ... OK
  Installing package openjdk-7u111b01-x86_64-1_SBo.tgz ... OK

openjdk8:
  MD5SUM check for icedtea-3.1.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-8u101b13-x86_64-1_SBo.tgz ... OK
  Installing package openjdk8-8u101b13-x86_64-1_SBo.tgz ... OK

so my initial guess is probably right. It probably has to do with race condition

USUARIONUEVO · 11-14-2016, 05:40 PM

Hi , make -j1 no help.

I think start to remove all xtra _SBo , and try again...i like to find the culprint.

USUARIONUEVO · 11-16-2016, 03:15 PM

rhino --> link broken

Alien Bob · 11-16-2016, 03:56 PM

Quote:

Originally Posted by willysr

I am able to build openjdk8 without issue here using sbopkg

The versions of OpenJDK (7 and 8) that you built are not the most recent ones by the way - security updates were released for both.