Re: 5.x packages and request for help.
Hi.
In <[EMAIL PROTECTED]>, Will Andrews wrote:
>Um.. objprelink is disabled if OSVERSION >= 500029. So it is
>already "ripped out" for -current.
>
I think it better to rip objprelink out of kde port on -CURRENT, too. On
my -CURRENT (updated in Mar 11), many kde binaries build with using
objprelink dump cores (I confirmed kde-config, artsd and so on.). And
they seems to work fine when I set NO_KDE_OBJPRELINK at build time. I
show a patch to disable objprelink on -CURRENT below. How about this,
Will?
diff -urN /usr/ports/audio/kdemultimedia2/Makefile audio/kdemultimedia2/Makefile
--- /usr/ports/audio/kdemultimedia2/MakefileFri Jan 18 00:00:19 2002
+++ audio/kdemultimedia2/Makefile Sat Mar 16 04:40:50 2002
@@ -28,13 +28,13 @@
CONFIGURE_ARGS+=--with-qt-includes=${X11BASE}/include/qt2 \
--with-qt-libraries=${X11BASE}/lib
-_NO_KDE_FINAL= yes
-.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
-
USE_GMAKE= yes
MAKE_ENV= ${CONFIGURE_ENV}
.include
+
+_NO_KDE_FINAL= yes
+.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
pre-configure:
${PERL} -pi -e "s@all_includes=\"@all_includes=\"-I/usr/include @g" \
diff -urN /usr/ports/deskutils/kdepim/Makefile deskutils/kdepim/Makefile
--- /usr/ports/deskutils/kdepim/MakefileWed Mar 6 00:01:08 2002
+++ deskutils/kdepim/Makefile Sat Mar 16 04:40:50 2002
@@ -24,6 +24,8 @@
INSTALLS_SHLIB=yes
GNU_CONFIGURE= yes
+.include
+
.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
QTCPPFLAGS=-I${LOCALBASE}/include -L${LOCALBASE}/lib
@@ -55,4 +57,4 @@
find ${WRKSRC}/libical -name Makefile.in | xargs ${PERL} -pi -e \
"s|INSTALL = \@INSTALL\@|INSTALL=${INSTALL} ${COPY} -o ${BINOWN} -g
${BINGRP}|g"
-.include
+.include
diff -urN /usr/ports/devel/kdesdk/Makefile devel/kdesdk/Makefile
--- /usr/ports/devel/kdesdk/MakefileSat Jan 12 00:01:13 2002
+++ devel/kdesdk/Makefile Sat Mar 16 04:40:50 2002
@@ -22,6 +22,8 @@
USE_BZIP2= yes
GNU_CONFIGURE= yes
+.include
+
.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
USE_GMAKE= yes
@@ -41,4 +43,4 @@
cd ${WRKSRC} && env PATH=${WRKSRC}/auto-bin:$$PATH \
${GMAKE} -f Makefile.cvs
-.include
+.include
diff -urN /usr/ports/devel/kdevelop/Makefile devel/kdevelop/Makefile
--- /usr/ports/devel/kdevelop/Makefile Sat Jan 12 00:01:13 2002
+++ devel/kdevelop/Makefile Sat Mar 16 04:40:50 2002
@@ -38,6 +38,8 @@
GNU_CONFIGURE= yes
CONFIGURE_ARGS+= --with-qtdoc-dir=${X11BASE}/share/doc/qt2/html
+.include
+
.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
pre-everything::
@@ -62,4 +64,4 @@
pre-build:
${PERL} -pi -e "[EMAIL PROTECTED]@libkdeui.so@g" ${WRKSRC}/kdevelop/main.cpp
-.include
+.include
diff -urN /usr/ports/editors/koffice/Makefile editors/koffice/Makefile
--- /usr/ports/editors/koffice/Makefile Sat Jan 12 00:01:47 2002
+++ editors/koffice/MakefileSat Mar 16 04:40:50 2002
@@ -26,6 +26,8 @@
GNU_CONFIGURE= yes
USE_GMAKE= yes
+.include
+
_NO_KDE_OBJPRELINK=yes
.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
@@ -56,4 +58,4 @@
${MV} ${PREFIX}/bin/kivio ${PREFIX}/bin/kivio.real
${INSTALL_SCRIPT} ${FILESDIR}/kivio.sh ${PREFIX}/bin/kivio
-.include
+.include
diff -urN /usr/ports/games/kdegames2/Makefile games/kdegames2/Makefile
--- /usr/ports/games/kdegames2/Makefile Sat Jan 12 00:02:15 2002
+++ games/kdegames2/MakefileSat Mar 16 04:40:50 2002
@@ -22,6 +22,8 @@
GNU_CONFIGURE= yes
USE_GMAKE= yes
+.include
+
.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
pre-configure:
@@ -35,4 +37,4 @@
cd ${WRKSRC} && env PATH=${WRKSRC}/auto-bin:$$PATH \
${GMAKE} -f Makefile.cvs
-.include
+.include
diff -urN /usr/ports/graphics/kdegraphics2/Makefile graphics/kdegraphics2/Makefile
--- /usr/ports/graphics/kdegraphics2/Makefile Sat Jan 12 00:02:37 2002
+++ graphics/kdegraphics2/Makefile Sat Mar 16 04:40:50 2002
@@ -26,9 +26,9 @@
USE_GMAKE= yes
CONFIGURE_ARGS+=--without-kamera
-.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
-
.include
+
+.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
# temporarily disable kamera, it requires gphoto2
PLIST_SUB+=KAMERA="@comment "
diff -urN /usr/ports/misc/kdeaddons/Makefile misc/kdeaddons/Makefile
--- /usr/ports/misc/kdeaddons/Makefile Sat Jan 12 00:04:12 2002
+++ misc/kdeaddons/Makefile Sat Mar 16 04:40:50 2002
@@ -27,9 +27,9 @@
PLIST_SUB+=RM=${RM}
CONFIGURE_ENV+=SDL_CONFIG="${LOCALBASE}/bin/sdl11-config"
-.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
-
.include
+
+.include "${.CURDIR}/../../x11/kde2/Makefile.kde"
pre-configure:
${MKDIR} ${WRKSRC}/auto-bin
diff -urN /usr/ports/misc/kdeutils2/Makefile misc/kdeutils2/Makefile
--- /usr/ports/misc/kdeutils2/Makefile Sat Jan 12 00:04:14 2002
+++ misc/kdeutils2/Makefile Sat Mar 16 04:40:50 2002
@@ -24,6 +24,8 @@
USE_GMAKE= yes
MAN1= efax.1
Re: 5.x packages and request for help.
Hi.
In <[EMAIL PROTECTED]>, Maxim M. Kazachek wrote:
>I've installed qt23 from ports painlessly
>
Does uic command provided by qt23 port work on your system? On my
-CURRENT (updated in Mar 11), that binary was linked with weird
liblcms.so_edata as next:
% ldd uic
uic:
libqutil.so.1 => /usr/X11R6/lib/libqutil.so.1 (0x28099000)
libqt2.so.4 => /usr/X11R6/lib/libqt2.so.4 (0x280a)
libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x28545000)
libm.so.2 => /usr/lib/libm.so.2 (0x2858a000)
libc_r.so.5 => /usr/lib/libc_r.so.5 (0x285a5000)
libc.so.5 => /usr/lib/libc.so.5 (0x285c3000)
liblcms.so_edata => not found (0x0)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x28676000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28684000)
libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x2875f000)
libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x28768000)
libXft.so.1 => /usr/X11R6/lib/libXft.so.1 (0x2877e000)
libpng.so.5 => /usr/local/lib/libpng.so.5 (0x287a7000)
libz.so.2 => /usr/lib/libz.so.2 (0x287c9000)
libjpeg.so.9 => /usr/local/lib/libjpeg.so.9 (0x287d6000)
libmng.so.1 => /usr/local/lib/libmng.so.1 (0x287f4000)
libXThrStub.so.6 => /usr/X11R6/lib/libXThrStub.so.6 (0x28826000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x28828000)
libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x2882d000)
liblcms.so.1 => /usr/local/lib/liblcms.so.1 (0x2886b000)
I don't know how to fix this. Only I can do is a makeshift disposition
as below:
diff -urN /usr/ports/x11-toolkits/qt23/Makefile qt23/Makefile
--- /usr/ports/x11-toolkits/qt23/Makefile Wed Feb 20 01:50:44 2002
+++ qt23/Makefile Sat Mar 16 05:59:21 2002
@@ -16,6 +16,8 @@
MAINTAINER?= [EMAIL PROTECTED]
+PLIST= ${WRKDIR}/pkg-plist
+
LIB_DEPENDS= mng.1:${PORTSDIR}/graphics/libmng \
png.5:${PORTSDIR}/graphics/png \
jpeg.9:${PORTSDIR}/graphics/jpeg
@@ -88,6 +90,13 @@
qt-pre-configure:
@true
+post-extract:
+ ${RM} -f ${PLIST}
+.if ${OSVERSION} >= 500029
+ ${ECHO_CMD} lib/liblcms.so_edata > ${PLIST}
+.endif
+ ${CAT} ${PKGDIR}/pkg-plist >> ${PLIST}
+
post-patch:
.if ${MACHINE_ARCH} == "i386" && !defined(NO_QT_OBJPRELINK)
.if !exists(${WRKDIR}/.${PKGNAME}.objprelink_patched)
@@ -170,6 +179,11 @@
.endfor
${INSTALL_MAN} ${WRKSRC}/doc/man/man3/q* ${PREFIX}/man/man3
.endif
+.endif
+
+post-install:
+.if ${OSVERSION} >= 500029
+ ${CP} ${LOCALBASE}/lib/libmng.so ${PREFIX}/lib/liblcms.so_edata
.endif
.include
Thank you.
--
SASAKI Katuhiro
mailto: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
I've recompiled kernet right before building qt... And have great prob with compiling -CURRENT right before Mar 8... I've installed -CURRENT SNAP on 20020219 which seems have broken binutils... Because xv and some other my packages coredumped with bus error (libpng issue, seemed to be solved Feb 22th) So, I was unable to compile -CURRENT after CVSup at Mar 6th (libpam issue), then was unable to run it (crypt_md5 bug). I was able to make -CURRENT up multiuser at Mar 11th, then deleted ALL packages and rebuilded from scratch... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Thu, 14 Mar 2002, Kris Kennaway wrote: >On Fri, Mar 15, 2002 at 08:36:29AM +0600, Maxim M. Kazachek wrote: >> I've installed qt23 from ports painlessly > >Fine, I'm glad to hear it :) > >The compile problems seem to be related to recent compiler toolchain >changes, which you might not see unless you recompiled everything qt23 >depends on from scratch (which the package cluster does). > >Kris > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
Hiten Pandya <[EMAIL PROTECTED]> writes: > I have a tru 5.0-CURRENT environment.. also.. is there any changes where > my ENABLE_NLS dillema can be solved.. s/dillema/dilemma/. It's not a dilemma, anyway; it's an issue, a condition, a situation, a problem, a failure; a conundrum (though not in the most usual sense of the word); a predicament; a jam, a fix, a (fine) pickle you've landed yourself in; possibly an impasse, if you really can't figure out a solution; an asperity, an exigency, or if you're in a hurry to get it fixed, maybe even an emergency - but definitely not a dilemma. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 05:54:40PM -0800, Alex Zepeda wrote: > As far as Qt goes, rip out that objprelink crap. Without it Qt will build > and work just fine. At least Qt 3.whatever works for me. I don't know > why objprelink isn't working correctly for Qt, but I don't really care. > For me disabling WITNESS does more than enough to make KDE useable on my > -current box (2xP2-450). Um.. objprelink is disabled if OSVERSION >= 500029. So it is already "ripped out" for -current. -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 09:01:47PM -0800, Terry Lambert wrote: > I think it's idiotic to put spackle over the broken window, > paint the wall, and then call it "fixed". I know what objprelink is, and as far as I'm concerned it's there to work around the substandard support that C++ gets from the GNU binutils and compiler. I don't feel much sympathy for the breaking a silly hack that amounts to spackle in the first place by whatever happened to the binutils. FWIW I haven't built KDE or Qt from the ports tree in a while. It seems like it's been about six days since I've cvsup'd and built world. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 10:16:14PM -0800, Peter Wemm wrote: > Alex Zepeda wrote: > > On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote: > > > > > The compile problems seem to be related to recent compiler toolchain > > > changes, which you might not see unless you recompiled everything qt23 > > > depends on from scratch (which the package cluster does). > > > > Right, when I tried to compile Qt3 recently I had problems with moc > > dupming core. Getting rid of any objprelink references solved that. I > > suggest that something similar be done in the port (maybe make objprelink > > optional and then off by default). > > The objprelink stuff should be fixed now, we need to know if it is not. > Have you built world recently (like, in the last day or two)? Do a > ls /usr/libdata/ldscripts, and if you do *not* see elf_i386.xc and > elf_i386.xsc, then your world is not new enough. I built a world after the recent ld commits, which failed to build qt23. I would have double-checked the tarball right away, except bento just died. fxp0: device timeout fxp0: device timeout [...] Kris msg36134/pgp0.pgp Description: PGP signature
Re: 5.x packages and request for help.
Alex Zepeda wrote: > On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote: > > > The compile problems seem to be related to recent compiler toolchain > > changes, which you might not see unless you recompiled everything qt23 > > depends on from scratch (which the package cluster does). > > Right, when I tried to compile Qt3 recently I had problems with moc > dupming core. Getting rid of any objprelink references solved that. I > suggest that something similar be done in the port (maybe make objprelink > optional and then off by default). The objprelink stuff should be fixed now, we need to know if it is not. Have you built world recently (like, in the last day or two)? Do a ls /usr/libdata/ldscripts, and if you do *not* see elf_i386.xc and elf_i386.xsc, then your world is not new enough. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
Alan Eldridge wrote: > On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote: > >Alex Zepeda wrote: > >> As far as Qt goes, rip out that objprelink crap. Without it Qt will build > >> and work just fine. At least Qt 3.whatever works for me. I don't know > >> why objprelink isn't working correctly for Qt, but I don't really care. > >> For me disabling WITNESS does more than enough to make KDE useable on my > >> -current box (2xP2-450). > > > >Uh, "objprelink" exists for a reason. It's not just decorative. > > I'll just point out that it's an optimization, and an optimization that > breaks a build is not particularly effective at optimizing anything. It's the tools change that breaks the optimization that breaks the build. THerefore it's the tools change that breaks the build. That's just simple root cause analysis. I think it's idiotic to put spackle over the broken window, paint the wall, and then call it "fixed". Working around tools problems removes the incentive to fix the tools. If you want the tools to get fixed, you won't put spackle everywhere the tools deficiencies show through to try to pretend the problems aren't there. This is a developer's release. As such, some things are expected to be broken, in order to cause people to fix the root cause of the problems. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote: > Alex Zepeda wrote: > > As far as Qt goes, rip out that objprelink crap. Without it Qt will build > > and work just fine. At least Qt 3.whatever works for me. I don't know > > why objprelink isn't working correctly for Qt, but I don't really care. > > For me disabling WITNESS does more than enough to make KDE useable on my > > -current box (2xP2-450). > > Uh, "objprelink" exists for a reason. It's not just decorative. Actually I thought it is; it was introduced in the ports system as a way to speed up runtime linking of KDE components, but KDE worked relatively well for years beforehand :) Kris msg36127/pgp0.pgp Description: PGP signature
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 08:25:39PM -0800, Terry Lambert wrote: >Alex Zepeda wrote: >> As far as Qt goes, rip out that objprelink crap. Without it Qt will build >> and work just fine. At least Qt 3.whatever works for me. I don't know >> why objprelink isn't working correctly for Qt, but I don't really care. >> For me disabling WITNESS does more than enough to make KDE useable on my >> -current box (2xP2-450). > >Uh, "objprelink" exists for a reason. It's not just decorative. I'll just point out that it's an optimization, and an optimization that breaks a build is not particularly effective at optimizing anything. -- Alan Eldridge "Dave's not here, man." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
Alex Zepeda wrote: > As far as Qt goes, rip out that objprelink crap. Without it Qt will build > and work just fine. At least Qt 3.whatever works for me. I don't know > why objprelink isn't working correctly for Qt, but I don't really care. > For me disabling WITNESS does more than enough to make KDE useable on my > -current box (2xP2-450). Uh, "objprelink" exists for a reason. It's not just decorative. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 06:56:53PM -0800, Alex Zepeda wrote:
> On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote:
>
> > The compile problems seem to be related to recent compiler toolchain
> > changes, which you might not see unless you recompiled everything qt23
> > depends on from scratch (which the package cluster does).
>
> Right, when I tried to compile Qt3 recently I had problems with moc
> dupming core. Getting rid of any objprelink references solved that. I
> suggest that something similar be done in the port (maybe make objprelink
> optional and then off by default).
Actually, I think you might have nailed it..
the qt23 port has this:
.if ${OSVERSION} >= 500029
NO_QT_OBJPRELINK= yes
.endif
but the portbuild script is still setting OSVERSION to 500027. I
thought I'd made all of those dynamic based on the version number in
the head of the CVS branch, but looks like I missed some.
Thanks!
Kris
msg36118/pgp0.pgp
Description: PGP signature
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 06:56:53PM -0800, Alex Zepeda wrote: > On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote: > > > The compile problems seem to be related to recent compiler toolchain > > changes, which you might not see unless you recompiled everything qt23 > > depends on from scratch (which the package cluster does). > > Right, when I tried to compile Qt3 recently I had problems with moc > dupming core. Getting rid of any objprelink references solved that. I > suggest that something similar be done in the port (maybe make objprelink > optional and then off by default). Any chance you could work me up a patch to test? Kris msg36117/pgp0.pgp Description: PGP signature
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 06:40:37PM -0800, Kris Kennaway wrote: > The compile problems seem to be related to recent compiler toolchain > changes, which you might not see unless you recompiled everything qt23 > depends on from scratch (which the package cluster does). Right, when I tried to compile Qt3 recently I had problems with moc dupming core. Getting rid of any objprelink references solved that. I suggest that something similar be done in the port (maybe make objprelink optional and then off by default). - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Fri, Mar 15, 2002 at 08:36:29AM +0600, Maxim M. Kazachek wrote: > I've installed qt23 from ports painlessly Fine, I'm glad to hear it :) The compile problems seem to be related to recent compiler toolchain changes, which you might not see unless you recompiled everything qt23 depends on from scratch (which the package cluster does). Kris msg36112/pgp0.pgp Description: PGP signature
Re: 5.x packages and request for help.
I've installed qt23 from ports painlessly Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote: > I'm just uploading a new 5.x package set. This run was better than > the previous (5364 packages vs. 5123 for the last run, but far fewer > than the 5973 packages which are building in 4.x), but there were > still a number of significant failures: qt2 is still failing so kde > doesn't build, and some of the gnome components also failed. As far as Qt goes, rip out that objprelink crap. Without it Qt will build and work just fine. At least Qt 3.whatever works for me. I don't know why objprelink isn't working correctly for Qt, but I don't really care. For me disabling WITNESS does more than enough to make KDE useable on my -current box (2xP2-450). - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
--- David O'Brien <[EMAIL PROTECTED]> wrote: > Will you be doing a run on a Tru5-CURRENT box? > Some of these it is hard to say anything about due to the very special > environment you built them under. I have a tru 5.0-CURRENT environment.. also.. is there any changes where my ENABLE_NLS dillema can be solved.. thanks, regards, -- Hiten Pandya -- <[EMAIL PROTECTED]> __ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 04:41:59PM -0800, David O'Brien wrote: > On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote: > > I'm just uploading a new 5.x package set. This run was better than > > the previous (5364 packages vs. 5123 for the last run, but far fewer > > than the 5973 packages which are building in 4.x), but there were > > still a number of significant failures: qt2 is still failing so kde > > doesn't build, and some of the gnome components also failed. > > Will you be doing a run on a Tru5-CURRENT box? > Some of these it is hard to say anything about due to the very special > environment you built them under. I suppose I'll have to try, but it's going to take me more effort to upgrade the clients. Please do what you can now: most of the problems are not kernel-related, and not caused by the build environment, and afaict it's only a few ports which try and use eaccess(2) which I need to upgrade for. Kris msg36103/pgp0.pgp Description: PGP signature
Re: 5.x packages and request for help.
On Thu, Mar 14, 2002 at 04:31:44PM -0800, Kris Kennaway wrote: > I'm just uploading a new 5.x package set. This run was better than > the previous (5364 packages vs. 5123 for the last run, but far fewer > than the 5973 packages which are building in 4.x), but there were > still a number of significant failures: qt2 is still failing so kde > doesn't build, and some of the gnome components also failed. Will you be doing a run on a Tru5-CURRENT box? Some of these it is hard to say anything about due to the very special environment you built them under. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.x packages and request for help.
Hi all, I'm just uploading a new 5.x package set. This run was better than the previous (5364 packages vs. 5123 for the last run, but far fewer than the 5973 packages which are building in 4.x), but there were still a number of significant failures: qt2 is still failing so kde doesn't build, and some of the gnome components also failed. Any porters who have some spare time, please visit http://bento.freebsd.org/errorlogs/5-latest/ and fix some ports; there are still a LOT of compile failures due to things like and ports which have not been fixed to work with XFree86-4. It's quite possible that some of the build failures are still spurious and caused by problems with the cluster, so please let me know of any "weird" failures which you think should not have happened. We have a developer preview snapshot coming up in a few weeks, so it's important that we get as many packages building as possible. Thanks in advance for your help. Kris msg36100/pgp0.pgp Description: PGP signature
