On 17 Dec 2005 08:51:01 -0800, Randal L. Schwartz wrote:
> By the way, I was thinking through my workaround, and have a
> hypothesis that binary cross-platform builds may actually be
> tainted... because that part of the build step must have been looking
> at *installed* include files, not just in
> "Hannah" == Hannah Schroeter <[EMAIL PROTECTED]> writes:
Hannah> Please don't. There're people who use the upgrade FAQ as it's intended
Hannah> (i.e. one may try it out, but one is on one's own, if things fail and
Hannah> one can't fix it, use binaries to get close to the revision(s) one wan
Hello!
On Fri, Dec 16, 2005 at 03:46:21PM -0700, Theo de Raadt wrote:
>[...]
>What do you suggest? Because the only other alternative is to DELETE
>the upgrade faq.
Please don't. There're people who use the upgrade FAQ as it's intended
(i.e. one may try it out, but one is on one's own, if thing
>Oh give it up. You are clearly not skilled enough to even compile
>code, let alone provide consulting services.
Everytime Theo speaks, I have some new quote materal.
woo
Randal L. Schwartz wrote:
>> "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
>
>>> I'm upgrading a remote box, so a "standard upgrade" is not an option,
>>> nor is a reinstall. There was no warning in the FAQ that the
>>> information was definitely broken. It must have worked for *someon
On Dec 16, 2005, at 6:00 PM, Jason Crawford wrote:
First off, I fail to see how extracting the install sets via ssh can't
be done, as that's mentioned in the FAQ as one upgrade method.
Upgrading via the install sets remotely works absolutely fine. I do
it every six months on a couple dozen bo
On 16 Dec 2005 14:41:38 -0800, Randal L. Schwartz wrote:
> > "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
>
> Theo> If you get stuck doing an upgrade build, please do a standard upgrade
> Theo> or reinstall.
>
> Theo> We have never promised that such builds will work perfectly, nor can
> "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
>> As it is, I worked out the problems. For the record, the workaround is:
>>
>> 1) remove the obj directory
Theo> Look, if you did not do this, you are an idiot.
However, what I meant was that this was in addition to the "don't do
the
> "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
>> I'm upgrading a remote box, so a "standard upgrade" is not an option,
>> nor is a reinstall. There was no warning in the FAQ that the
>> information was definitely broken. It must have worked for *someone*
>> or it wouldn't have been p
Oh give it up. You are clearly not skilled enough to even compile
code, let alone provide consulting services.
> > "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
>
> >> As it is, I worked out the problems. For the record, the workaround is:
> >>
> >> 1) remove the obj directory
>
> T
> >> I'm upgrading a remote box, so a "standard upgrade" is not an option,
> >> nor is a reinstall. There was no warning in the FAQ that the
> >> information was definitely broken. It must have worked for *someone*
> >> or it wouldn't have been put in the FAQ, I presume.
>
> Theo> Oh, but you do
On 16 Dec 2005 14:41:38 -0800, Randal L. Schwartz wrote:
>
> I'm upgrading a remote box, so a "standard upgrade" is not an option,
> nor is a reinstall. There was no warning in the FAQ that the
> information was definitely broken. It must have worked for *someone*
> or it wouldn't have been put
> I'm upgrading a remote box, so a "standard upgrade" is not an option,
> nor is a reinstall. There was no warning in the FAQ that the
> information was definitely broken. It must have worked for *someone*
> or it wouldn't have been put in the FAQ, I presume.
Oh, but you don't understand.
Yes,
> "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes:
Theo> If you get stuck doing an upgrade build, please do a standard upgrade
Theo> or reinstall.
Theo> We have never promised that such builds will work perfectly, nor can we
Theo> dedicate 3-4 developers full-time to making sure they do.
If you get stuck doing an upgrade build, please do a standard upgrade
or reinstall.
We have never promised that such builds will work perfectly, nor can we
dedicate 3-4 developers full-time to making sure they do. Which is
pretty much what it would take.
> >From http://openbsd.org/faq/upgrade-ol
>From http://openbsd.org/faq/upgrade-old.html
I see that I need to issue the following:
# cd /usr/src/gnu/lib/libstdc++
# make -f Makefile.bsd-wrapper cleandir
# make -f Makefile.bsd-wrapper obj
# make -f Makefile.bsd-wrapper
# make -f Makefile.bsd-wrapper install
I have
16 matches
Mail list logo
