[SOLVED] Searching gcc-go-8.1.1-arm-1

Pigi_102 · 02-20-2020, 05:00 AM

Hi all,
I'm searching the package ( txz ) file for gcc-go for arm, in the version 8.1.1
I'm not well sure why in my installation ( sarpi 14.2 ) __NOT__ upgraded to current the installed gcc is 8.1.1.
Actually I would not upgrade to current that implies quite a bit of downtime to get all running.

So I'm asking if someone has the gcc-go version as in subject, or eventually some slackbuild for it.

Any chance to find it ?

Thanks in advance

Pierluigi

drmozes · 02-20-2020, 09:21 AM

Quote:

Originally Posted by Pigi_102

Hi all,
I'm searching the package ( txz ) file for gcc-go for arm, in the version 8.1.1
I'm not well sure why in my installation ( sarpi 14.2 ) __NOT__ upgraded to current the installed gcc is 8.1.1.
Actually I would not upgrade to current that implies quite a bit of downtime to get all running.

So I'm asking if someone has the gcc-go version as in subject, or eventually some slackbuild for it.

Any chance to find it ?

Thanks in advance

Pierluigi

Slackware ARM 14.2 has gcc 5.5.0. There are no newer versions of that package available for this release of the distribution.
You cannot put packages from -current onto a Slackware ARM 14.2 installation - they are incompatible entirely.

Slackware ARM -current currently has gcc 9.2.0. Any older packages are not available unless someone happens to have an older version of it that they can share with you; but you'd be better to update if you are actually running -current (which you say you aren't).

Pigi_102 · 02-20-2020, 09:40 AM

Thanks for your reply, drmozes.

I know 14.2 and -current are incompatibles but...

Code:

root@casa:~# cat /etc/slackware-version 
Slackware 14.2

and packages in /var/adm/packages are dated 01 01 1970 ( which is the classical date of an installation done without an internet access to set the date) and so are all the others, thus IMHO this has been a single phase install.

Code:

root@casa:~# ls -l /var/adm/packages/gcc*
-rw-r--r-- 1 root root 43449 Jan  1  1970 /var/adm/packages/gcc-8.1.1-arm-1
-rw-r--r-- 1 root root 42761 Jan  1  1970 /var/adm/packages/gcc-g++-8.1.1-arm-1
-rw-r--r-- 1 root root  2195 Jan  1  1970 /var/adm/packages/gcc-objc-8.1.1-arm-1
-rw-r--r-- 1 root root   780 Jan  1  1970 /var/adm/packages/gccmakedep-1.0.3-arm-2

as are all other packages.

I can't really understand what's happened and I think I will go -current as I need golang.

What I was asking infact was if someone has an old rsync mirror or similar, to avoid the huge impact of an update to the -current ( old slackware user, here

) or even worse a gcc recompile that on a raspberry PI3 will probably takes forever.

Unfortunally ( or luckily ? ) I've customized so much stuff around that a reinstall is not desiderable, nor possible

Thanks for your time in any case.

Pierluigi

drmozes · 02-20-2020, 09:54 AM

Quote:

Originally Posted by Pigi_102

Thanks for your reply, drmozes.

Code:

root@casa:~# cat /etc/slackware-version 
Slackware 14.2

-current has a '+' to indicate it's no longer the previous stable release.

Code:

root@zippy:~# cat /etc//slackware-version
Slackware 14.2+

As yours does not have this, your system seems to be messed up. I don't know if you've installed the 'aaa_base' package from -current onto 14.2 or something else.

Code:

root@zippy:~# readelf -h /bin/bash|grep float
  Flags:                             0x5000400, Version5 EABI, hard-float ABI

Run that on your machine: if it does not say 'hard-float', it is 14.2.

Quote:

I can't really understand what's happened and I think I will go -current as I need golang.

What I was asking infact was if someone has an old rsync mirror or similar, to avoid the huge impact of an update to the -current ( old slackware user, here

) or even worse a gcc recompile that on a raspberry PI3 will probably takes forever.

Unfortunally ( or luckily ? ) I've customized so much stuff around that a reinstall is not desiderable, nor possible

You cannot do an inplace update to -current: it's a full reformat, reinstall.
And since there was never a gcc-8 package for 14.2, nobody will have one.
If you're running 14.2 then that gcc-8 package is from -current quite some time ago, and won't work.

The first thing you need to do is figure out what version of the OS you're running by running the command above.

Pigi_102 · 02-20-2020, 11:43 AM

Code:

root@casa:~# readelf -h /bin/bash|grep float
  Flags:                             0x5000400, Version5 EABI, hard-float ABI

Seems I'm on current, isn't it ?

I've read a lot from several thread about HF or SF, and according with this last command is definitivelly an HF, which indeed say that is a -current.

Also glibc is a 2.27 which wasn't in 14.2 but was in current ( on 2018, somewhere around july ) so my guess is that slackware-release is wrong.

In any case I'm backing up my sd card an will try a slackpkg update/install-new/upgrade-all/clean-system cycle ( if the ext3 for backup works ) and let you know

Sometime luck is on our side

drmozes · 02-20-2020, 11:52 AM

Quote:

Originally Posted by Pigi_102

Code:

root@casa:~# readelf -h /bin/bash|grep float
  Flags:                             0x5000400, Version5 EABI, hard-float ABI

Seems I'm on current, isn't it ?

I've read a lot from several thread about HF or SF, and according with this last command is definitivelly an HF, which indeed say that is a -current.

Also glibc is a 2.27 which wasn't in 14.2 but was in current ( on 2018, somewhere around july ) so my guess is that slackware-release is wrong.

In any case I'm backing up my sd card an will try a slackpkg update/install-new/upgrade-all/clean-system cycle ( if the ext3 for backup works ) and let you know

Sometime luck is on our side

Yep - that looks good for an upgrade. I'd probably reinstall from scratch though - it's might be faster depending on how much stuff you'd have to migrate to the new system. When I was a sysadmin I always kept a map of each server/server type, so I knew which configs/dirs to bring over to an upgraded system; and any software packages I'd build Slackware packages for, and let pkgtools take care of that.

Good luck! :-)

Pigi_102 · 02-22-2020, 05:32 AM

I have successfully upated to latest -current and so I can use the gcc-go from there.

Thanks Stuart !

Pigi