Date: Sun, 13 Jun 2004 00:12:48 -0700 From: Sean McNeil <sean@mcneil.com> To: Tom Cage <k5gj@earthlink.net> Cc: freebsd-amd64@freebsd.org Subject: Re: amd64 FreeBSD update Message-ID: <1087110768.2136.0.camel@server.mcneil.com> In-Reply-To: <1087110679.1924.29.camel@server.mcneil.com> References: <40CB951A.50208@earthlink.net> <1087110679.1924.29.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ooops! forgot to add -amd64 :) On Sun, 2004-06-13 at 00:11, Sean McNeil wrote: > Tom, > > I hope you do not mind, but I think your experiences would be very > beneficial to post on freebsd-amd64. Frankly, I think that mailing list > is being underutilized right now. I hope that increased activity with > messages like this will help the people involved to increase the quality > of amd64 support and functionality. > > Most people are extremely busy trying to get certain desired > functionality into freebsd/amd64 that things like this get lost without > this kind of feedback. IMHO, your weekly attempts to get the > functionality your desire and your successes/failures is invaluable and > a great indicator of things that should be looked into. I, for one, > appreciate hearing about your experiences. > > On Sat, 2004-06-12 at 16:43, Tom Cage wrote: > > Sean, > > > > I performed my weekly upgrade on my AMD64 Saturday afternoon. > > > > Gigabyte GA-K8VT800M motherboard (AMD64-3400+) > > K8-2200, 64K L1, 1M L2, FSB 800MHz, 1024M DDR400 PC3200, Bus 200MHz > > > > The basic world/kernel worked fine for > > # make buildworld > > # make buildkernel KERNCONF=MYKERNEL > > # make installkernel KERNCONF=MYKERNEL > > | > > # make installworld > > | > > > > gigabyte# uname -a > > FreeBSD gigabyte.k5gj 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sat Jun 12 > > 15:00:13 CDT 2004 > > root@gigabyte.k5gj:/usr/obj/usr/src/sys/MYKERNEL amd64 > > gigabyte# > > IIRC, you are doing a dual boot and every week you have been rebuilding > everything as mentioned above starting with the system in whatever state > is was in the previous week. You are not reloading from a baseline and > then performing the update. Correct? Except at the end you talk about > scrubbing the hard drive. Are you installing a fresh release CD each > time? > > > /******************************************************************************/ > > > > However, most of the ports have not been upgraded. Some of these > > are i386 > > binaries, for instance: > > > > gigabyte# cd /usr/ports/misc/cpuid > > [snip] > ONLY_FOR_ARCHS= i386 > [snip] > > yes, cpuid will complain if you try to install it. I guess you should > pkg_delete it until it has been fixed to work with amd64. > > > Note that in lsof, the build starts with version 4.71.3 and fails with > > version 4.72C??? > > > > gigabyte5# cd /usr/ports/sysutils/lsof > > gigabyte5# make install clean > > ===> Building for lsof-4.71.3 > > (cd lib; make DEBUG="-O" CFGF="-pipe -funroll-loops -DHASCPUMASK_T > > -DFREEBSDV=5020 -DHASFDESCFS=2 -DHASNULLFS -DHASIPv6 > > -DLSOF_VSTR=\"5.2-CURRENT\"") > > cc -pipe -funroll-loops -DHASCPUMASK_T -DFREEBSDV=5020 -DHASFDESCFS=2 > > -DHASNULLFS -DHASIPv6 -DLSOF_VSTR=\"5.2-CURRENT\" -I -O -c dnode.c > > dnode.c: In function `process_node': > > dnode.c:583: error: `pn' undeclared (first use in this function) > > dnode.c:583: error: (Each undeclared identifier is reported only once > > dnode.c:583: error: for each function it appears in.) > > dnode.c:589: error: `pnp' undeclared (first use in this function) > > *** Error code 1 > > > > Stop in /usr/ports/sysutils/lsof/work/lsof_4.72C.freebsd. > > *** Error code 1 > > > > Stop in /usr/ports/sysutils/lsof. > > You should probably send this to the maintainer: obrien@FreeBSD.org > > > /******************************************************************************/ > > > > NTL has not been upgraded to version 5.3.2 which is needed for amd64 > > compatibility. > > > > gigabyte5# cd /usr/ports/math/ntl > > gigabyte# cat Makefile > [snip] > > MAINTAINER= matthiasb@acm.org > [snip] > > Can you email matthias on that? Either ask for it to be updated or > disabled for amd64. > > > /******************************************************************************/ > > > > Lastly, KDE still has the same problem with x86_64 not being compatible > > with shared objects. > [snip] > > /usr/bin/ld: .libs/dcopstub.o: relocation R_X86_64_32S can not be used > > when making a shared object; recompile with -fPIC > > This appears to be a problem with libtool. The cheap solution for me > was to add to /etc/make.conf > > CFLAGS= -O -pipe -fPIC > > when building packages like this. Marcus has also committed a patch to > the Makefile for evolution that fixes this issue. Perhaps you could see > if that modification would help for this package as well. > > There is also the possibility of doing a pkg_delete of all the installed > libtool packages and then trying again that it may use a libtool that > works properly. I don't know. > > > /******************************************************************************/ > > /******************************************************************************/ > > /******************************************************************************/ > > > > Thus, I have great hopes for RC3 when it comes out. I will scrub the > > hard drive and start fresh. > > Thanks again, > Sean >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1087110768.2136.0.camel>