On Wed, 28 Jun 2000, Mark Murray wrote:
> > > Adding something to bootstrap-tools implies that we can't use the
> > > installed miniperl (backward compatibility problem) or the host doesn't
> > > have miniperl. The bootstrap-tools built miniperl would then be used
> > > throughout the build and
> > Adding something to bootstrap-tools implies that we can't use the
> > installed miniperl (backward compatibility problem) or the host doesn't
> > have miniperl. The bootstrap-tools built miniperl would then be used
> > throughout the build and install stages.
>
> I think that's what we have
> I am not sure who is supposed to manage the fact that
> /usr/ports/Mk/bsd.ports.mk doesn't yet know about perl-5.006. One
> appears to need to set PERL_VER and PERL_VERSION. I just added an ."if
> {OSVERSION} >= 56" , but this clearly isn't enough for people who
> have yet to upgrade to th
> The choice to use crosstools is easier, since it by default installs the
> tool into the "strict path", but Mark used build-tools and a path to
> miniperl to do it instead, presumably since it is restricted to a very
> minor bit of the tree.
Also because miniperl and libperl want libm, and that
Mark:
Got through the buildworld with a recent cvsup. I am now running with
this "world". Many thanks.
I am not sure who is supposed to manage the fact that
/usr/ports/Mk/bsd.ports.mk doesn't yet know about perl-5.006. One
appears to need to set PERL_VER and PERL_VERSION. I just added an ."if
On Tue 2000-06-27 (02:41), John Baldwin wrote:
>
> On 26-Jun-00 David O'Brien wrote:
> > On Mon, Jun 26, 2000 at 10:28:53PM +0200, Mark Murray wrote:
> >> > Since I'm now through it, I don't know the latest problem, but the
> >> > last thing I saw that the old lib got used with the new perl (or t
On 26-Jun-00 David O'Brien wrote:
> On Mon, Jun 26, 2000 at 10:28:53PM +0200, Mark Murray wrote:
>> > Since I'm now through it, I don't know the latest problem, but the
>> > last thing I saw that the old lib got used with the new perl (or the
>> > other way round) and that looks like it can be fi
> > Ok. I'll re-cvsup now and take a peek.
>
> Got all the ${MINIPERL} stuff, and I now have a successful
> buildworld. Took 7 minutes longer than the last time though...
I'm glad it worked! The "Yes, it is cool now" reports are just as
valuable as the "You idiot! You broke it!" ones :-)
M
--
Hi
Thanks - this is the line that I am working on; your debugging is
valuable!!
M
> I have found that the following small diff to /usr/src/Makefile.inc1
> allows the buildworld to proceed:
>
> *** Makefile.inc1~ Mon Jun 26 23:00:54 2000
> --- Makefile.inc1 Mon Jun 26 23:27:05 2000
>
On Tue, Jun 27, 2000 at 02:52:51PM -0500, Ade Lovett wrote:
> Mark wrote:
> > (Look for lots of ${MINIPERL} in place of "miniperl").
>
> Ok. I'll re-cvsup now and take a peek.
Got all the ${MINIPERL} stuff, and I now have a successful
buildworld. Took 7 minutes longer than the last time though
> It breaks further down the line when building
> /usr/src/gnu/usr.bin/perl/perl, with the following message:
>
> lib/auto/DynaLoader/DynaLoader.a(DynaLoader.o): In function `SaveError':
> DynaLoader.o(.text+0x1e2): undefined reference to `Perl_vmess'
This is a library problem, and I have nearly
On Tue, Jun 27, 2000 at 09:48:59PM +0200, Mark Murray wrote:
> > Just for the record, I tried that.. (my laptop is at 06/20 -current
> > right now)
>
> What "right now"? I committed some fixes about 4 hours ago. Do you
> have those?
"right now" as in "it's running kernel and userland from 06/20"
> Just for the record, I tried that.. (my laptop is at 06/20 -current
> right now)
What "right now"? I committed some fixes about 4 hours ago. Do you
have those?
(Look for lots of ${MINIPERL} in place of "miniperl").
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubs
[cc's trimmed]
On Mon, Jun 26, 2000 at 10:08:58PM +0200, Mark Murray wrote:
> > Message to others for bootstrapping:
> >
> > Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624,
> > build and install it manually, then update both dirs to HEAD and do a
> > world with the new perl
"George W. Dinolt" wrote:
>
> I have found that the following small diff to /usr/src/Makefile.inc1
> allows the buildworld to proceed:
>
It breaks further down the line when building
/usr/src/gnu/usr.bin/perl/perl, with the following message:
lib/auto/DynaLoader/DynaLoader.a(DynaLoader.o): In
I have found that the following small diff to /usr/src/Makefile.inc1
allows the buildworld to proceed:
*** Makefile.inc1~ Mon Jun 26 23:00:54 2000
--- Makefile.inc1 Mon Jun 26 23:27:05 2000
***
*** 123,129
WORLDTMP= ${OBJTREE}${.CURDIR}/${BUILD_ARCH}
# /usr/gam
> It is possible the Perl build Makefiles have a slight bogon that prevents
> things from working properly in this stage?
:-) Uh Huh!
> > > Note that bootstrap-tools are built (and installed under /obj) to be run
> >
> > OK - I'll try again fro build-tools.
>
> I tried that (on my Alpha). Sam
On Tue, Jun 27, 2000 at 08:08:15AM +0200, Mark Murray wrote:
> What you say supports the theory that build-tools is the answer; however
> build-tools seems to want to do an in-place build - not to install the
> tool(s) somewhere into the path like cross-tools. I'm in trouble with
> cross-tools bec
> > I thought build-tools was the answer; sadly that seems to be wrong.
> > Now I'm looking at cross-tools (out of src/makefile.inc1).
>
> Adding something to bootstrap-tools implies that we can't use the
> installed miniperl (backward compatibility problem) or the host doesn't
> have miniperl.
On Mon, Jun 26, 2000 at 10:28:53PM +0200, Mark Murray wrote:
> > Since I'm now through it, I don't know the latest problem, but the
> > last thing I saw that the old lib got used with the new perl (or the
> > other way round) and that looks like it can be fixed with some path
> > adjustments.
>
>
It seems Mark Murray wrote:
> > If I'm not mistaken, all open problems are like "Perl lib version
> > (v5.6.0) doesn't match executable version (5.00503) at Config.pm line
> > 18."
>
> Hmm...
>
> > That should be easy to reproduce on your development system by just
> > copying an old /usr/bin/pe
> If I'm not mistaken, all open problems are like "Perl lib version
> (v5.6.0) doesn't match executable version (5.00503) at Config.pm line
> 18."
Hmm...
> That should be easy to reproduce on your development system by just
> copying an old /usr/bin/perl executable to it and trying to build.
Wh
> Since I'm now through it, I don't know the latest problem, but the
> last thing I saw that the old lib got used with the new perl (or the
> other way round) and that looks like it can be fixed with some path
> adjustments.
The problem here is that miniperl needs to be built early enough
to be i
In <[EMAIL PROTECTED]>, Mark Murray wrote:
> > Message to others for bootstrapping:
> >
> > Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624,
> > build and install it manually, then update both dirs to HEAD and do a
> > world with the new perl in place.
>
> Now you can colour
In <[EMAIL PROTECTED]>, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Martin Cracauer writes:
> : [CC'ed to current]
> : Message to others for bootstrapping:
> :
> : Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624,
> : build and install it manually, then update both dir
> Message to others for bootstrapping:
>
> Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624,
> build and install it manually, then update both dirs to HEAD and do a
> world with the new perl in place.
Now you can colour me flummoxed. :-(.
Have you a script(1) of that?
M
--
M
In message <[EMAIL PROTECTED]> Martin Cracauer writes:
: [CC'ed to current]
:
: In <[EMAIL PROTECTED]>, Martin Cracauer wrote:
: > In <[EMAIL PROTECTED]>, Mark Murray wrote:
: > > May I have a login on your build box to have a look?
: >
: > It would be more useful if you could put a log of you
[CC'ed to current]
In <[EMAIL PROTECTED]>, Martin Cracauer wrote:
> In <[EMAIL PROTECTED]>, Mark Murray wrote:
> > May I have a login on your build box to have a look?
>
> It would be more useful if you could put a log of your buildworld (at
> least the perl-related parts) somewhere so I can l
28 matches
Mail list logo
