just following up on myself for anyone who might make the same mistake...
turns out i had not read-recently or forgotten how to "follow -current"
correctly...
https://www.openbsd.org/faq/current.html
in particular, i had downloaded a snapshot and dd'ed onto a usb-stick but
chosen (I)nstall
when
symptom: did a "pkg_add wget" on a recent-snapshot fails with bad-major
c++ errors... am i being impatient also ?
i remember reading (07-08 jan) that the pkg_add compiles were taking awhile
to grind thru... it is also quite-possible that i have hit a gap between
the snapshot i downloaded and
> While at it, link /bin/ls to /bin/rm
An Apple fanboy trying to look 1337 in a linux style on an OpenBSD mailing list.
Impressive not.
On Jan 07 21:30, Christian Weisgerber wrote:
> A new build is running now and will take another 24h to complete
> if all goes well.
Thanks for the ETA. You build ports faster than I can. I appreciate
your service.
On Jan 07 16:40:37, ch...@nmedia.net wrote:
> For those trying to use the latest snap and the latest ports, try link
> libc++.so.4.0 to libc++.so.5.0 and libc++abi.so.2.1 to libc++abi.so.3.0
> for now. Frankenstein, indeed. You'll feel dirty just doing it.
While at it, link /bin/ls to /bin/rm
On Thu, Jan 07, 2021 at 09:30:13PM +0100, Christian Weisgerber wrote:
| Steve Williams:
|
| > I hesitate to send this because perhaps I'm just too impatient, but then
| > again, perhaps not. This is not critical/time sensitive.
| >
| > I just thought I'd check if there a problem with the
On 2021-01-07, Patrick Wildt wrote:
> Maybe I should have asked ports to run with the build first, so that
> base and packages would be aligned.
We (package builders) don't really do that - and in the majority of
cases it's not much of a problem anyway, it normally only affects people
that have
On Thu, Jan 07, 2021 at 05:44:05PM -0700, Theo de Raadt wrote:
> Chris Cappuccio wrote:
>
> > Mihai Popescu [mih...@gmail.com] wrote:
> > > I was in the same situation, impatient to have a 2021 snapshot.
> > >
> > > Warning: I am not sure you will not finish with a Frankenstein system. I
> > >
Chris Cappuccio wrote:
> Mihai Popescu [mih...@gmail.com] wrote:
> > I was in the same situation, impatient to have a 2021 snapshot.
> >
> > Warning: I am not sure you will not finish with a Frankenstein system. I am
> > not so good with compiler-linker stuff.
>
> For those trying to use the
Mihai Popescu [mih...@gmail.com] wrote:
> I was in the same situation, impatient to have a 2021 snapshot.
>
> Warning: I am not sure you will not finish with a Frankenstein system. I am
> not so good with compiler-linker stuff.
For those trying to use the latest snap and the latest ports, try
I was in the same situation, impatient to have a 2021 snapshot.
Dirty hint: the .hk mirror still has the base part from 2020! But try it as
a last option, the folks there are not so bandwidth fortunate. After
installing the base, please switch /etc/installurl to something more
suitable as
On 07/01/2021 1:30 p.m., Christian Weisgerber wrote:
Steve Williams:
I hesitate to send this because perhaps I'm just too impatient, but then
again, perhaps not. This is not critical/time sensitive.
I just thought I'd check if there a problem with the current packages folder
from the
Steve Williams:
> I hesitate to send this because perhaps I'm just too impatient, but then
> again, perhaps not. This is not critical/time sensitive.
>
> I just thought I'd check if there a problem with the current packages folder
> from the mirrors?
No, the amd64 package builds have been
Thanks for the correction!
amit
On Thu, Jan 7, 2021 at 11:59 AM Patrick Wildt wrote:
>
> No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been
> committed. This issue is because of libunwind 11. With libc++ 11 we
> have made a separate ports build first, to check the
Impatient it is :D
Thanks for the update!
Cheers,
Steve W.
On 07/01/2021 10:56 a.m., Patrick Wildt wrote:
I committed an update to libunwind which made a major bump necessary.
Maybe I should have asked ports to run with the build first, so that
base and packages would be aligned. Too late
Oh, and another correction: it's libc++ 10.0.1, we're not going 11 yet.
Am Thu, Jan 07, 2021 at 06:59:52PM +0100 schrieb Patrick Wildt:
> No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been
> committed. This issue is because of libunwind 11. With libc++ 11 we
> have made a
No, that's not correct. The libc++ 11 (*not* LLVM 11) has not yet been
committed. This issue is because of libunwind 11. With libc++ 11 we
have made a separate ports build first, to check the fallout. Once the
fallout is mostly fixed, we'll do the switch to libc++ 11. Until then
snapshots are
Like naddy@ mentioned on ports@ they are trying to figure out the
fallout from the switch to LLVM 11 as system compiler. This is why the
packages are being delayed. Please wait a while till it is sorted out.
thanks
On Thu, Jan 7, 2021 at 10:56 AM Steve Williams
wrote:
>
> Hi,
>
> I hesitate to
I committed an update to libunwind which made a major bump necessary.
Maybe I should have asked ports to run with the build first, so that
base and packages would be aligned. Too late for that now. Time will
fix it though.
Am Thu, Jan 07, 2021 at 09:54:39AM -0700 schrieb Steve Williams:
> Hi,
>
Hi,
I hesitate to send this because perhaps I'm just too impatient, but then
again, perhaps not. This is not critical/time sensitive.
I just thought I'd check if there a problem with the current packages
folder from the mirrors?
I am trying to update my development system (to resume work
20 matches
Mail list logo
