2024/09/29

Newest at the top

2024-09-29 17:30:37 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-09-29 17:24:23 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 17:22:27 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-09-29 17:17:16 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 17:16:24 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 17:07:56 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 17:06:51 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 252 seconds)
2024-09-29 17:06:35 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-09-29 17:06:14 +0200hiecaq`(~hiecaq`@user/hiecaq) hiecaq
2024-09-29 17:01:28 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 17:01:17 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2024-09-29 16:53:03 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-09-29 16:49:57 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 276 seconds)
2024-09-29 16:49:40 +0200edwtjo(~edwtjo@fsf/member/edwtjo) edwtjo
2024-09-29 16:49:40 +0200edwtjo(~edwtjo@h-85-24-143-221.A213.priv.bahnhof.se) (Changing host)
2024-09-29 16:49:40 +0200edwtjo(~edwtjo@h-85-24-143-221.A213.priv.bahnhof.se)
2024-09-29 16:49:18 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 16:47:49 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 16:42:05 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2024-09-29 16:40:34 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 260 seconds)
2024-09-29 16:39:58 +0200ultralan(~warty@ipservice-092-217-187-046.092.217.pools.vodafone-ip.de) (Remote host closed the connection)
2024-09-29 16:39:42 +0200ultralan(~warty@ipservice-092-217-187-046.092.217.pools.vodafone-ip.de) ultralan
2024-09-29 16:37:06 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-09-29 16:36:03 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 16:34:25 +0200misterfish(~misterfis@178-85-89-58.dynamic.upc.nl) misterfish
2024-09-29 16:34:00 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 16:33:34 +0200sp1ff(~user@c-73-11-70-111.hsd1.wa.comcast.net) (Remote host closed the connection)
2024-09-29 16:32:02 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 16:30:44 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 16:27:01 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) raehik
2024-09-29 16:22:23 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 16:21:02 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-09-29 16:19:26 +0200 <dontdieych2> there must be some compiler flags for set manually to so.5
2024-09-29 16:18:36 +0200 <dontdieych2> bunch of warnings about libinfo
2024-09-29 16:18:29 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 248 seconds)
2024-09-29 16:17:46 +0200Vengeance(~Vengeance@2.219.56.221) (Ping timeout: 265 seconds)
2024-09-29 16:17:22 +0200 <dontdieych2> -b 9.4.8 , is it right? (whatever, nothing to lose)
2024-09-29 16:16:57 +0200 <dontdieych2> hope to it works
2024-09-29 16:16:44 +0200 <dontdieych2> started ` ghcup compile ghc -j 4 -v 9.4.8 -b 9.4.8`
2024-09-29 16:16:16 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 16:15:21 +0200Vengeance_(~Vengeance@2.219.56.221)
2024-09-29 16:12:49 +0200 <int-e> (but I'd also expect to run into trouble with subprocesses that actually want .6)
2024-09-29 16:12:03 +0200 <int-e> . o O ( I /might/ consider LD_PRELOAD shenanigans depending on mood and phase of the moon )
2024-09-29 16:11:23 +0200 <int-e> dontdieych2: okay. sorry this is probably not helpful because apparently that ghc links against .6. I was mostly curious.
2024-09-29 16:09:05 +0200 <geekosaur> include files won't match
2024-09-29 16:08:54 +0200 <dontdieych2> manually `ln -sf` /lib64/libtinfo.so -> libtinfo.so.5 ?
2024-09-29 16:08:06 +0200 <geekosaur> won't help with rebuilding it unless there's a libtinfo.so pointing to the 5.9 so and matching include files, though
2024-09-29 16:08:02 +0200 <dontdieych2> so.. tinfo.so.5 is there but whatever reason ghc grab so.6?
2024-09-29 16:07:32 +0200 <dontdieych2> .rw-r--r--@ 448k root root 1 Feb 09:00 /lib64/libtinfo_g.a
2024-09-29 16:07:30 +0200 <dontdieych2> .rwxr-xr-x@ 335k root root 1 Feb 09:00 /lib64/libtinfo.so.6.4*