Re: [Slackbuilds-users] 32-bit fails

Paz, 2022-03-27 tarihinde 11:24 -0400 saatinde, B. Watson yazdı: > > G. Ignore all that I said in that email. It doesn't actually > work, we would need a newer glibc for that. > > I was looking at the manual for glibc-2.35, but our glibc is 2.33. > > And I thought it worked because I was

Re: [Slackbuilds-users] Name clash

On 28/3/22 10:58, Arnaud via SlackBuilds-users wrote: > The submission queue is also for updates. > It is mandatory for new packages. > > - Yth. > Since I maintain the existing SlackBuild dcmtk and I didn't submit a change, I presume the dcmtk.tar.gz in the pending queue is a new submission

Re: [Slackbuilds-users] Updated ftbfs list

On Sun, Mar 27, 2022, 2:13 PM B. Watson wrote: > > > On Sun, 27 Mar 2022, Jeremy Hansen wrote: > > > > > Where do you go to find how Debian builds its packages? I know about the > AUR > > for Arch and Gentoo's gitweb. > > Search for the package name on https://www.debian.org/distrib/packages > >

Re: [Slackbuilds-users] Name clash

The submission queue is also for updates. It is mandatory for new packages. - Yth. Le 27 mars 2022 21:41:20 UTC, Christoph Willing a écrit : >After I submitted a new SlackBuild, I checked that it existed in the >pending queue. Right after my own submission, I noticed another >submission for a

[Slackbuilds-users] failed to download source list

Here's a few more I've come across, including the 3 I mentioned in #slackbuilds. #The following are easily fixed with sbofindsrc: development/flawfinder development/latrace development/s51dude network/csync network/mod_auth_kerb network/mod_geoip2 network/pgbouncer network/sslstrip

[Slackbuilds-users] Name clash

After I submitted a new SlackBuild, I checked that it existed in the pending queue. Right after my own submission, I noticed another submission for a SlackBuild which already exists - dcmtk.tar.gz Assuming the new submission is for new _different_ software, the name will have to be changed.

Re: [Slackbuilds-users] 32-bit fails

On Sun, 27 Mar 2022, Lenard Spencer wrote: If all fails, unless anything on SBo absolutely needs openjdk 6 or 7, we may have to just drop those two. No, if all else fails, we'd have to mark them as unsupported on 32-bit. They build fine on 64-bit, don't they? It'd be nicer to have them

Re: [Slackbuilds-users] Updated ftbfs list

On Sun, 27 Mar 2022, Jeremy Hansen wrote: Where do you go to find how Debian builds its packages? I know about the AUR for Arch and Gentoo's gitweb. Search for the package name on https://www.debian.org/distrib/packages When I was updating handbrake to the latest version to allow

Re: [Slackbuilds-users] 32-bit fails

I am now officially asking for help on openjdk7 32-bit. When it is linking the launcher, it wants to link in libstdc++.so from /usr/lib (from gcc11), instead of /usr/lib/gcc/i586-slackware-linux/5.5.0 (same with openjdk6). They built fine with -current back on June 8. Openjdk8 builds fine with

Re: [Slackbuilds-users] Updated ftbfs list

Le 27/03/2022 à 20:24, Luc Van Rompaey a écrit : > > I would go to https://www.debian.org/distrib/packages > and scroll down to "Search package > directories". There you can enter a keyword (e.g., "Handbrake", verify that > the > "Package names only"

Re: [Slackbuilds-users] Updated ftbfs list

Il giorno dom 27 mar 2022 alle ore 20:07 Jeremy Hansen < jebrhansen+...@gmail.com> ha scritto: > Where do you go to find how Debian builds its packages? I know about the > AUR for Arch and Gentoo's gitweb. > there's also https://sources.debian.org there search for handbrake, click on the

Re: [Slackbuilds-users] Updated ftbfs list

Op zo 27 mrt. 2022 om 20:07 schreef Jeremy Hansen : > On Fri, Mar 25, 2022, 1:19 AM B. Watson wrote: > >> >> >> On Thu, 24 Mar 2022, Ozan Türkyılmaz wrote: >> >> > News on HandBrake: >> > First of all, it seems HandBrake does not support 32bit compile anymore >> > [1]. However, someone did get

Re: [Slackbuilds-users] Updated ftbfs list

On Fri, Mar 25, 2022, 1:19 AM B. Watson wrote: > > > On Thu, 24 Mar 2022, Ozan Türkyılmaz wrote: > > > News on HandBrake: > > First of all, it seems HandBrake does not support 32bit compile anymore > > [1]. However, someone did get it compile it as 32bit [2] with disabling > > x265. I know x265

Re: [Slackbuilds-users] 32-bit fails

On Sun, 27 Mar 2022, B. Watson wrote: Actually... I looked into it a bit more... we *have* 64-bit time_t support in glibc, on Slackware 15.0. It works like large file support, you "#define _TIME_BITS 64" before including or . Doesn't break the ABI, it causes your code to be compiled with

Re: [Slackbuilds-users] 32-bit fails

On Sun, 27 Mar 2022, Ozan Türkyılmaz wrote: Cum, 2022-03-25 tarihinde 11:56 -0400 saatinde, B. Watson yazdı: On Fri, 25 Mar 2022, Ozan Türkyılmaz wrote: The y2k38 issue... there's now kernel support for a 64-bit time_t on 32-bit, but AFAICT no support in glibc. That's a big ABI break. I

Re: [Slackbuilds-users] 32-bit fails

Cum, 2022-03-25 tarihinde 11:56 -0400 saatinde, B. Watson yazdı: > > > On Fri, 25 Mar 2022, Ozan Türkyılmaz wrote: > > The y2k38 issue... there's now kernel support for a 64-bit time_t on > 32-bit, but AFAICT no support in glibc. > That's a big ABI break. I am not surprised they are holding it