Date: Sun, 5 May 2002 09:29:27 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: obrien@FreeBSD.ORG Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: kdebase3 Message-ID: <15573.13239.472652.640403@grasshopper.cs.duke.edu> In-Reply-To: <20020504221948.B1043@dragon.nuxi.com> References: <20020504151121.A1813@dragon.nuxi.com> <15572.24953.530925.959853@grasshopper.cs.duke.edu> <20020504221948.B1043@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien writes: > On Sat, May 04, 2002 at 06:32:25PM -0400, Andrew Gallatin wrote: > > Anyway, what's happening seems to be the build process somehow causes > > the configure script to get rebuilt after our port starts the build > > (eg, the .configure_done.kdebase-3.0_1 is there _before_ the configure > > script grows an "-O2" & is re-run). > > This suggests a problem with your clock (or something else); such that > gmake thinks something is out of date and needs to rerun configure. Something is causing it to be re-run: % ls -l work/kdebase-3.0/configure work/.configure_done.kdebase-3.0_1 -rw-r--r-- 1 gallatin wheel 0 May 4 18:20 work/.configure_done.kdebase-3.0_1 -rwxr-xr-x 1 gallatin wheel 1089599 May 4 18:21 work/kdebase-3.0/configure* And this isn't an x86 w/ACPI or something, my clock only runs one direction ;) > > > I think our autoconf is part of the problem, as it sets the cflags to > > O2. So, I've hit the autoconf port over the head with this patch: > > autoconf isn't being run when building the kdebase3 port. So this patch, Its being run out of gmake itself after the port is configured. Take a peek at http://people.freebsd.org/~gallatin/kde.log.gz > could be useful maybe, but will not help you with kdebase3. > (but the patch would totally screw me when submitting things back to FSF) > > > And the kdebase3 port with this: > > +pre-configure: > > + ${PERL} -pi -e "s@-O2@-O@g" ${WRKSRC}/configure > > + ${PERL} -pi -e "s@-O2@-O@g" ${WRKSRC}/aclocal.m4 > > + ${PERL} -pi -e "s@-O2@-O@g" ${WRKSRC}/admin/acinclude.m4.in > > + ${PERL} -pi -e "s@-O2@-O@g" ${WRKSRC}/admin/libtool.m4.in > > The aclocal.m4 (and maybe all the .m4 files) should not need this patch > -- as we aren't regenerating `configure'. The patch to configure would > fix your problem -- but I think it is just masking the real problem. One of them was the magic bullet, I'm not sure which. I'm going to start pulling things out one by one & see when the O2 creeps back in. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15573.13239.472652.640403>