Den fre 20 nov. 2020 kl 15:09 skrev Roderick :
> > obsolete even on your 6.7 install.. i386 has been a default clang arch
> > since OpenBSD /6.2/.
>
> Clang was default, gcc may be obsolete, but /usr/bin/gcc is till now
> there, broken. In the upgrade instructions is not mentioned to delete
> it:
On Fri, Nov 20, 2020 at 02:02:56PM +, Rodrigo Readi wrote:
>
> On Fri, 20 Nov 2020, Bryan Steele wrote:
>
> > It took you *6* emails before finally mentioning which platform were
> > on, even after being asked..
>
> Yes, excuse me, I answered to Nick Samsung nc10, but not mentioned i386.
>
On Fri, 20 Nov 2020, Bryan Steele wrote:
It took you *6* emails before finally mentioning which platform were
on, even after being asked..
Yes, excuse me, I answered to Nick Samsung nc10, but not mentioned i386.
i386 removed the base gcc compiler in OpenBSD 6.6, so the binaries were
Your
On Fri, Nov 20, 2020 at 11:27:46AM +, Roderick wrote:
>
> On Thu, 19 Nov 2020, Todd C. Miller wrote:
>
> > On Thu, 19 Nov 2020 22:07:33 +, Roderick wrote:
> >
> > > g++, gcc and gcov in /bin are from Apr 13, 2019. The rest are from
> > > Oct 5, 2020.
> >
> > That explains your problem.
Roderick wrote:
> It seems, gcc was removed from i386. That explains the old date of my
gcc binary that was never deleted.
It took you *6* emails before finally mentioning which platform were
on, even after being asked..
i386 removed the base gcc compiler in OpenBSD 6.6, so the binaries were
obso
On Nov 20 11:27:46, hru...@gmail.com wrote:
>
> On Thu, 19 Nov 2020, Todd C. Miller wrote:
>
> > On Thu, 19 Nov 2020 22:07:33 +, Roderick wrote:
> >
> > > g++, gcc and gcov in /bin are from Apr 13, 2019. The rest are from
> > > Oct 5, 2020.
> >
> > That explains your problem. The upgrade w
On Thu, 19 Nov 2020, Todd C. Miller wrote:
On Thu, 19 Nov 2020 22:07:33 +, Roderick wrote:
g++, gcc and gcov in /bin are from Apr 13, 2019. The rest are from
Oct 5, 2020.
That explains your problem. The upgrade would have removed any
obsolete /usr/lib/gcc-lib/amd64-unknown-openbsd* di
Thanks you both, Nick, Todd!
On Thu, 19 Nov 2020, Todd C. Miller wrote:
There should now be a /usr/lib/gcc-lib/amd64-unknown-openbsd6.8
directory for use by the updated gcc/g++ but for some reason you
don't have those updated gcc binaries.
I do not even have a directory /usr/lib/gcc-lib, bu
On Thu, 19 Nov 2020 22:07:33 +, Roderick wrote:
> g++, gcc and gcov in /bin are from Apr 13, 2019. The rest are from
> Oct 5, 2020.
That explains your problem. The upgrade would have removed any
obsolete /usr/lib/gcc-lib/amd64-unknown-openbsd* directory which
the old gcc binaries require.
T
On Thu, 19 Nov 2020, Nick Holland wrote:
Worst case, unload all pacakges, then go through the /usr, /bin and /bin
directories looking for files older than your current install, and
removing
them (most of them aren't bad. But something isn't right). Then do
another upgrade to whatever you wan
Upgraded from 6.7 to 6.8 in a very nice Samsung nc10 nettop.
Upgrade with sysupgrade, third time done with it. As I remember, I always
followed carefully the instructions.
The problem arose, I suspect, on 6.6 (upgraded, but did not use it
to much) or on 6.7.
I wanted to run gcc that I always
On 2020-11-19 08:36, Roderick wrote:
>
> broken gcc is the old gcc, the one of the package is installed as egcc.
>
> Do only I have a broken gcc?
>
> R.
>
> On Thu, 19 Nov 2020, Roderick wrote:
>
>>
>> After upgrading, I still have gcc, but no package gcc.
>>
>> I get the above error. I get it
broken gcc is the old gcc, the one of the package is installed as egcc.
Do only I have a broken gcc?
R.
On Thu, 19 Nov 2020, Roderick wrote:
After upgrading, I still have gcc, but no package gcc.
I get the above error. I get it also after installing gcc, and also after
deinstalling it, ma
After upgrading, I still have gcc, but no package gcc.
I get the above error. I get it also after installing gcc, and also after
deinstalling it, making "pkg_delete -a" and reinstalling.
Any hint, what can I do?
Thanks.
R.
14 matches
Mail list logo
