serpente has quit [Remote host closed the connection]
<brian|lfs>
jaeger, this is painful on my 13900k when I compiling when I have a threadripper 7980x lol
<jaeger>
your 13900k has as many threads as my 2nd gen threadripper, I'm unsympathetic :P
SiFuh__ has joined #crux
SiFuh_ has quit [Ping timeout: 260 seconds]
SiFuh_ has joined #crux
SiFuh__ has quit [Ping timeout: 260 seconds]
lavaball has joined #crux
lavaball has quit [Remote host closed the connection]
ppetrov^ has joined #crux
lavaball has joined #crux
darfo_ has joined #crux
darfo has quit [Ping timeout: 260 seconds]
mhtgw has joined #crux
<mhtgw>
good morning, just trying to get connected on support for crux first time.
<pitillo>
morning mhtgw, so this is probably a good place for that
<mhtgw>
@pitillo, thank you. just wanted to check does anyone know if there is end of life process in crux? trying to use crux-3.7 because of a requirement of gcc-6.5.0.
<pitillo>
CRUX 3.7 was shipped with gcc 12.2.0, wasn't it?
<mhtgw>
yes
<pitillo>
so aren't you able to use gcc-6.5.0 with gcc 14.2.0?
<mhtgw>
my idea is not go after latest of packages but to stop at the last stable versions and that is where i am trying to stop at crux-3.7 regardless of the gcc version. and gcc-6.5.0 is the need.
<pitillo>
I'm not sure, but I think 3.7 should be not updated anymore... may be it takes security updates merged from 3.8
<pitillo>
my doubt is about gcc 6.5.0 version. Do you have it ported and got it working on CRUX 3.7?
<cruxbridge>
<tim> CRUX 3.8 is discontinued
<pitillo>
*CRUX 3.7
<cruxbridge>
<tim> oops, right
<cruxbridge>
<tim> :D
lavaball has quit [Ping timeout: 252 seconds]
lavaball has joined #crux
ppetrov^ has quit [Quit: Leaving]
<mhtgw>
@pitillo, i see it is still getting updated however was checking if there is a formal process of end-of-life for any version or if each version is supported.
<mhtgw>
crux-3.7 to be specific.
<mhtgw>
i am compiling the crux-3.7 packages with gcc-6.5.0.
<mhtgw>
just to avoid multiple gcc versions.
<cruxbridge>
<tim> mhtgw: core 3.7 branch saw the last update three months ago. There have been a few minor updates pushed in opt/contrib but you can expect that there will be none anymore now
<mhtgw>
got it, tim.
<cruxbridge>
<tim> Do you mind telling us what you are trying to get going here? For what do you need gcc that old and why would you want to replace an updated gcc with the old one?
<cruxbridge>
<tim> you only said that gcc 6 is what you need, not what its for. But anyway, its your best option if you ask me. Compiling all of 3.7 with gcc that old I am sure that you will run in a lot of problems.
<cruxbridge>
<tim> Instead of compiling all with an that old gcc, you should compile the one that needs it with that.
<cruxbridge>
<tim> it's easy to override in the Pkgfile
<mhtgw>
it is more of the shoulder and the hand problem where if the shoulder does not move then the hand does not move even if the hand thinks it is moving. my plan is stick with the older gcc version that works as much as possible because it is very clean.