I think it is necessary to add the notice to UPDATING because it's been
half an year since the incident day. If it were like within last few
days, I definitely would've gotten some hints about the fix by scanning
-current (which I did). But I had to scratch my heads helplessly until
I asked the
On Sat, Dec 01, 2001 at 01:26:11PM -0800, Eugene M. Kim wrote:
> Oh, never mind. I just re-read the thread you pointed (thanks) and
> saw it affects the systems *installed around the breakage date*.
>
> UPDATING does not mention about this fact (it simply says `Building
> perl was broken'); perh
Oh, never mind. I just re-read the thread you pointed (thanks) and saw
it affects the systems *installed around the breakage date*.
UPDATING does not mention about this fact (it simply says `Building perl
was broken'); perhaps it should be updated to mention the misfortune of
the installed syste
Well, I *did* read UPDATING, and I saw the perl breakage notice. But it
seems not to be relevant to me, as my source code is current (I mean, up
to date); I cvsupped it just before starting make world. Only my host
system is built around May 1.
Thanks,
Eugene
On Sat, Dec 01, 2001 at 05:18:45PM
On Thu, Nov 29, 2001 at 10:42:45AM -0800, Eugene M. Kim wrote:
> Hello,
>
> I am getting the following error in the make depend stage; could anyone
> shed a light?
>
> (The host system is 5-current as of around May 1.)
>From UPDATING (you do read UPDATING, don't you?):
20010502:
Perl b
Hello,
I am getting the following error in the make depend stage; could anyone
shed a light?
(The host system is 5-current as of around May 1.)
Thanks,
Eugene
snip snip
===> libperl
===> miniperl
===> perl
Extracting config.h (with
