Re: nvidia-driver 64bit version
> OK, wine is working. I did a minimal install so lib32 was missing. I > installed nvidia-driver 32bit into the chroot and now World of > Warcraft is working! 32bit glxgears is working too. I will say on a OT note, I play World of Warcraft on FreeBSD. and I am getting almost identical performance in amd64 FreeBSD 8. as I get on the Same machine with OSX 10.5.8 (aka ideneb) the FPS is within 1 -4 fps difference. FreeBSD is better when you mount the /tmp with TMPFS but to be fair I have not tried to use a memory backed /tmp drive on OSX Sam Fourman Jr. Fourman Networks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Mon, Dec 7, 2009 at 19:55, Marius Nünnerich wrote: > On Fri, Dec 4, 2009 at 19:56, Sam Fourman Jr. wrote: >> On Fri, Dec 4, 2009 at 10:20 AM, Robert Noland wrote: >>> On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote: On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > Hi > > I was wondering if you're working on a port for the 64bit version of > the new beta state nvidia driver [1]. Yup, thanks for the pointer. I'm considering options right now. > > Since it's a completely different version it should IMO be separate from > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver > could be renamed to x11/nvidia-driver-i386. This would be the easiest route, but I'm not sure this is the best thing to do. From user's perspective, one should be able to "cd category/port" and "make install". The rest (including taking care of architecture-dependent things) should be handled by underlying infrastructure. Right now I believe our bpm is capable of the task, and my pmake/bpm-fu is strong enough, we'll see. >>> >>> I've never actually used the blob, but is the new driver only amd64? I >>> presume that it does need at least 8.0-RELEASE to work, but I can't >> >> it also works with RELENG_7 (but not 7.2R) >> as a side note, I installed wine in a 32bit chroot and installed the >> 32bit version of the new nvidia driver >> and I can Play World of Warcraft without any issues, so I guess it >> works Just like linux does. > > OK, I try to do the same, except on 8.0-RELEASE. How did you do that? > I followed > http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d > but whenever I execute > % wine32 > ELF interpreter /libexec/ld-elf.so.1 not found > zsh: abort LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib PATH= > > % alias wine32 > wine32='LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib > PATH=/compat/i386/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/marius/bin:/usr/local/kde4/bin > /compat/i386/usr/local/bin/wine' > > > btw. glxgears works not chrooted. > OK, wine is working. I did a minimal install so lib32 was missing. I installed nvidia-driver 32bit into the chroot and now World of Warcraft is working! 32bit glxgears is working too. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 4, 2009 at 19:56, Sam Fourman Jr. wrote: > On Fri, Dec 4, 2009 at 10:20 AM, Robert Noland wrote: >> On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote: >>> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: >>> > Hi >>> > >>> > I was wondering if you're working on a port for the 64bit version of >>> > the new beta state nvidia driver [1]. >>> >>> Yup, thanks for the pointer. I'm considering options right now. >>> >>> > >>> > Since it's a completely different version it should IMO be separate from >>> > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver >>> > could be renamed to x11/nvidia-driver-i386. >>> >>> This would be the easiest route, but I'm not sure this is the best thing >>> to do. From user's perspective, one should be able to "cd >>> category/port" and "make install". The rest (including taking care of >>> architecture-dependent things) should be handled by underlying >>> infrastructure. Right now I believe our bpm is capable of the task, and >>> my pmake/bpm-fu is strong enough, we'll see. >> >> I've never actually used the blob, but is the new driver only amd64? I >> presume that it does need at least 8.0-RELEASE to work, but I can't > > it also works with RELENG_7 (but not 7.2R) > as a side note, I installed wine in a 32bit chroot and installed the > 32bit version of the new nvidia driver > and I can Play World of Warcraft without any issues, so I guess it > works Just like linux does. OK, I try to do the same, except on 8.0-RELEASE. How did you do that? I followed http://wiki.freebsd.org/Wine#head-6963d527c173e57b1567e881305b544d33435b6d but whenever I execute % wine32 ELF interpreter /libexec/ld-elf.so.1 not found zsh: abort LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib PATH= % alias wine32 wine32='LD_32_LIBRARY_PATH=/compat/i386/usr/local/lib PATH=/compat/i386/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/marius/bin:/usr/local/kde4/bin /compat/i386/usr/local/bin/wine' btw. glxgears works not chrooted. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Alexey, Alexey Dokuchaev wrote: > On Fri, Dec 04, 2009 at 03:35:47PM +, Alexey Dokuchaev wrote: >> In any case, I'll post a diff here for review before I make any commits >> WRT amd64 support in nvidia-driver. > > OK, see attached diff. I could not test amd64 version, because my amd64 > box is currently down, but will certainly do so once it's up'n'running > again. i386 version works fine so far. > > I would appreciate any testing (esp. amd64) of the patched port. Please > note that some changes in pkg-list occurred; try to see that port > deinstalls cleanly in amd64 case (both via "make deinstall" and > "pkg_delete"). And, of course, that it installs and works. uname -a: FreeBSD vic.hcn-strela.ru 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Dec 4 00:48:18 MSK 2009 r...@vic.hcn-strela.ru:/usr/obj/usr/src/sys/VIC amd64 4Gb, 8800GTX. Installs: cleanly Deinstalls: cleanly pkg_delete: cleanly Works: yes (tested native app: ioquake3; linux apps: googleearth, linux-quake4) Thank you very much for the port! > > Thanks. > > ./danfe - -- Best regards, Victor Popov mailto:v.a.po...@gmail.com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkscPhoACgkQtKisLOtMPvniLgCg0+RJ6+reLMTapNzULZB00Hfz qvYAoM5xNFireXGY1YbDZ+t1/mFW1vON =FLi/ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 04, 2009 at 03:35:47PM +, Alexey Dokuchaev wrote:
> In any case, I'll post a diff here for review before I make any commits
> WRT amd64 support in nvidia-driver.
OK, see attached diff. I could not test amd64 version, because my amd64
box is currently down, but will certainly do so once it's up'n'running
again. i386 version works fine so far.
I would appreciate any testing (esp. amd64) of the patched port. Please
note that some changes in pkg-list occurred; try to see that port
deinstalls cleanly in amd64 case (both via "make deinstall" and
"pkg_delete"). And, of course, that it installs and works.
Thanks.
./danfe
Index: Makefile
===
RCS file: /mnt/fbsd/development/FreeBSD-CVS/ports/x11/nvidia-driver/Makefile,v
retrieving revision 1.93
diff -u -r1.93 Makefile
--- Makefile29 Sep 2009 13:25:25 - 1.93
+++ Makefile6 Dec 2009 20:56:53 -
@@ -6,18 +6,23 @@
#
PORTNAME= nvidia-driver
-DISTVERSION?= 185.18.36
+DISTVERSION?= 195.22
PORTREVISION?= 0 # As a reminder it can be overridden
CATEGORIES=x11 kld
MASTER_SITES= ${MASTER_SITE_NVIDIA}
+ARCH_SUFX= ${ARCH:S/i386//:S/amd/_/}
+.if ${DISTVERSION} == 195.22
+MASTER_SITE_SUBDIR=XFree86/FreeBSD-x86${ARCH_SUFX}/${DISTVERSION}
+ONLY_FOR_ARCHS=i386 amd64
+.else
MASTER_SITE_SUBDIR=freebsd/${DISTVERSION}
-DISTNAME= NVIDIA-FreeBSD-x86-${DISTVERSION}
+ONLY_FOR_ARCHS=i386
+.endif
+DISTNAME= NVIDIA-FreeBSD-x86${ARCH_SUFX}-${DISTVERSION}
MAINTAINER=da...@freebsd.org
COMMENT= NVidia graphics card binary drivers for hardware OpenGL
rendering
-ONLY_FOR_ARCHS=i386
-
NO_PACKAGE=should be recompiled for a particular FreeBSD kernel
USE_GL=gl
USE_LDCONFIG= yes
@@ -27,8 +32,11 @@
PORTDOCS= *
OPTIONS= FREEBSD_AGP "Use FreeBSD AGP GART driver" off \
- ACPI"Enable support for ACPI Power Management" off \
+ ACPI_PM "Enable support for ACPI Power Management" off \
LINUX "Build with support for Linux compatibility" on
+.if ${DISTVERSION} == 195.22
+OPTIONS+= WBINVD "Enable heavy-weight cache-flush logic" off
+.endif
# Starting with version 1.0-7667, NVidia has dropped support for numerous
# "legacy" GPUs. Consult NVidia README (the Appendix) to find out whether
@@ -37,7 +45,7 @@
# slave ports.
#
# XXX Until NVidia starts to name their releases consistently, employ this
-# ugly hack to derive NVVERSION. XXX
+# ugly hack below to derive NVVERSION. XXX
#
.if ${DISTVERSION:C/[0-9]+//g} == ".." # major.minor.update
NVVERSION= ${DISTVERSION:S/.//g}
@@ -80,7 +88,7 @@
${REINPLACE_CMD} -E 's/undef (NV_SUPPORT_OS_AGP)/define \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
-.if defined(WITH_ACPI)
+.if defined(WITH_ACPI_PM)
${REINPLACE_CMD} -E 's/undef (NV_SUPPORT_ACPI_PM)/define \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
@@ -88,8 +96,12 @@
${REINPLACE_CMD} -E 's/define (NV_SUPPORT_LINUX_COMPAT)/undef \1/' \
${WRKSRC}/src/nv-freebsd.h
.endif
+.if defined(WITH_WBINVD)
+ ${REINPLACE_CMD} -E 's/undef (NV_USE_WBINVD)/define \1/' \
+ ${WRKSRC}/src/nv-freebsd.h
+.endif
# Don't build any binaries (nvidia-settings and nvidia-xconfig) and manuals
-.if ${NVVERSION} < 974600
+.if ${NVVERSION} < 974600 || ${NVVERSION} == 1952200
${REINPLACE_CMD} -E 's/(extension).*/\1/' ${WRKSRC}/x11/Makefile
.else
${REINPLACE_CMD} -E 's/(lib).*/\1/' ${WRKSRC}/x11/Makefile
@@ -111,7 +123,7 @@
.if ${NVVERSION} < 817400
@${REINPLACE_CMD} '/libnvidia-cfg/d' ${TMPPLIST}
.endif
-.if ${NVVERSION} < 974600
+.if ${NVVERSION} < 974600 || ${NVVERSION} == 1952200
@${REINPLACE_CMD} '/wfb/d' ${TMPPLIST}
.endif
.if ${NVVERSION} < 1802900
Index: distinfo
===
RCS file: /mnt/fbsd/development/FreeBSD-CVS/ports/x11/nvidia-driver/distinfo,v
retrieving revision 1.33
diff -u -r1.33 distinfo
--- distinfo29 Sep 2009 13:25:25 - 1.33
+++ distinfo6 Dec 2009 18:19:43 -
@@ -1,6 +1,9 @@
-MD5 (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) = feff4da79a8c3a2f194f46c95c545adb
-SHA256 (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) =
890b9543d3c81bccc72d60c653647a719c9037f8fc7a88144a18b2a012fbd4a7
-SIZE (NVIDIA-FreeBSD-x86-185.18.36.tar.gz) = 19245550
+MD5 (NVIDIA-FreeBSD-x86-195.22.tar.gz) = 2c7faa5baa155693be978c446c5d44a3
+SHA256 (NVIDIA-FreeBSD-x86-195.22.tar.gz) =
2299aeadeec81a1210d65529c17c2829fdc4d5586c46b1ae6f8b20089a2122e8
+SIZE (NVIDIA-FreeBSD-x86-195.22.tar.gz) = 24784839
+MD5 (NVIDIA-FreeBSD-x86_64-195.22.tar.gz) = c9b0cdeb68d573556a38e16c02ffed55
+SHA256 (NVIDIA-FreeBSD-x86_64-195.22.tar.gz) =
3a6a0fc3003615c07090c04f2d5b41fa86cf8493309bf48eff8bcaa37126508c
+SIZE (NVIDIA-FreeBSD-x86_64-195.22.tar.gz
Re: nvidia-driver 64bit version
On Fri, 4 Dec 2009 15:18:29 + Alexey Dokuchaev wrote: > On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > > Hi > > > > I was wondering if you're working on a port for the 64bit version of > > the new beta state nvidia driver [1]. > > Yup, thanks for the pointer. I'm considering options right now. Have nVidia said anything about releasing 64-bit versions of the legacy drivers? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 4, 2009 at 10:20 AM, Robert Noland wrote: > On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote: >> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: >> > Hi >> > >> > I was wondering if you're working on a port for the 64bit version of >> > the new beta state nvidia driver [1]. >> >> Yup, thanks for the pointer. I'm considering options right now. >> >> > >> > Since it's a completely different version it should IMO be separate from >> > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver >> > could be renamed to x11/nvidia-driver-i386. >> >> This would be the easiest route, but I'm not sure this is the best thing >> to do. From user's perspective, one should be able to "cd >> category/port" and "make install". The rest (including taking care of >> architecture-dependent things) should be handled by underlying >> infrastructure. Right now I believe our bpm is capable of the task, and >> my pmake/bpm-fu is strong enough, we'll see. > > I've never actually used the blob, but is the new driver only amd64? I > presume that it does need at least 8.0-RELEASE to work, but I can't it also works with RELENG_7 (but not 7.2R) as a side note, I installed wine in a 32bit chroot and installed the 32bit version of the new nvidia driver and I can Play World of Warcraft without any issues, so I guess it works Just like linux does. Sam Fourman Jr. Fourman Networks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 04, 2009 at 10:20:10AM -0600, Robert Noland wrote: > I've never actually used the blob, but is the new driver only amd64? I > presume that it does need at least 8.0-RELEASE to work, but I can't > imagine that the underlying code would be different for i386/amd64. Driver we talk about is beta 195.22, and it exists for both i386 and amd64. It officially supports FreeBSD 7.2 with a current RELENG_7 kernel (>= 702106; use of a top-of-tree RELENG_7 kernel is recommended to ensure recent Linux ABI compatibility fixes are picked up); 8.0 is also supported: http://www.nvnews.net/vbulletin/showthread.php?t=142120 ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, 4 Dec 2009, Robert Noland wrote: *snip* I've never actually used the blob, but is the new driver only amd64? I presume that it does need at least 8.0-RELEASE to work, but I can't imagine that the underlying code would be different for i386/amd64. i.e. the new driver *should* be better on both i386 and amd64, at least if they have compiled an i386 version. My understanding is that the blob is the same on all platforms. The driver may be the same (or close). The package is different. While both ship with Linux x86 libraries, they contain only the FreeBSD libraries specific to the platform (amd64 or i386). I do still wish that nvidia would join the rest of the modern world and decide to release docs and code like every other vendor, but that is a different debate I suppose. I concur, yet I am very happy at the moment to see them support FreeBSD amd64. Sean -- s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, 2009-12-04 at 15:18 +, Alexey Dokuchaev wrote: > On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > > Hi > > > > I was wondering if you're working on a port for the 64bit version of > > the new beta state nvidia driver [1]. > > Yup, thanks for the pointer. I'm considering options right now. > > > > > Since it's a completely different version it should IMO be separate from > > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver > > could be renamed to x11/nvidia-driver-i386. > > This would be the easiest route, but I'm not sure this is the best thing > to do. From user's perspective, one should be able to "cd > category/port" and "make install". The rest (including taking care of > architecture-dependent things) should be handled by underlying > infrastructure. Right now I believe our bpm is capable of the task, and > my pmake/bpm-fu is strong enough, we'll see. I've never actually used the blob, but is the new driver only amd64? I presume that it does need at least 8.0-RELEASE to work, but I can't imagine that the underlying code would be different for i386/amd64. i.e. the new driver *should* be better on both i386 and amd64, at least if they have compiled an i386 version. I do still wish that nvidia would join the rest of the modern world and decide to release docs and code like every other vendor, but that is a different debate I suppose. robert. > ./danfe > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 04, 2009 at 04:25:22PM +0100, Rainer Hurling wrote: > On 04.12.2009 16:18 (UTC+1), Alexey Dokuchaev wrote: > > Right now I believe our bpm is capable of the task, and > > my pmake/bpm-fu is strong enough, we'll see. > > I tried it with patching your Makefile and distinfo. In Makefile I only > changed DISTVERSION and DISTNAME and commented out ONLY_FOR_ARCHS. > > It installs fine and as far as I can see now all is well :-) > > This is on 9.0-CURRENT (amd64) from today. Good to hear. I expect few things would require some adjustments (OPTIONS and packaging list come to mind first), but the fact port works with just your simple changes is definitely a good sign. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 04, 2009 at 04:32:11PM +0100, Emanuel Haupt wrote: > > On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > > > Hi > > > > > > I was wondering if you're working on a port for the 64bit version of > > > the new beta state nvidia driver [1]. > > > > Yup, thanks for the pointer. I'm considering options right now. > > > > > > > > Since it's a completely different version it should IMO be separate > > > from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and > > > x11/nvidia-driver could be renamed to x11/nvidia-driver-i386. > > > > This would be the easiest route, but I'm not sure this is the best > > thing to do. From user's perspective, one should be able to "cd > > category/port" and "make install". The rest (including taking care of > > architecture-dependent things) should be handled by underlying > > infrastructure. Right now I believe our bpm is capable of the task, > > and my pmake/bpm-fu is strong enough, we'll see. > > Right, you can put shared make functionality in a separate file and > include it by both ports. Personally I'd prefer two separate ports > rather than OPTIONS because the two drivers don't provide the same > functionality (ie missing TRIM support) and have different versions. In any case, I'll post a diff here for review before I make any commits WRT amd64 support in nvidia-driver. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
> On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > > Hi > > > > I was wondering if you're working on a port for the 64bit version of > > the new beta state nvidia driver [1]. > > Yup, thanks for the pointer. I'm considering options right now. > > > > > Since it's a completely different version it should IMO be separate > > from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and > > x11/nvidia-driver could be renamed to x11/nvidia-driver-i386. > > This would be the easiest route, but I'm not sure this is the best > thing to do. From user's perspective, one should be able to "cd > category/port" and "make install". The rest (including taking care of > architecture-dependent things) should be handled by underlying > infrastructure. Right now I believe our bpm is capable of the task, > and my pmake/bpm-fu is strong enough, we'll see. Right, you can put shared make functionality in a seperate file and include it by both ports. Personally I'd prefer two seperate ports rather than OPTIONS because the two drivers don't provide the same funcionality (ie missing TRIM support) and have different versions. Emanuel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On 04.12.2009 16:18 (UTC+1), Alexey Dokuchaev wrote: On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: Hi I was wondering if you're working on a port for the 64bit version of the new beta state nvidia driver [1]. Yup, thanks for the pointer. I'm considering options right now. Since it's a completely different version it should IMO be separate from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver could be renamed to x11/nvidia-driver-i386. This would be the easiest route, but I'm not sure this is the best thing to do. From user's perspective, one should be able to "cd category/port" and "make install". The rest (including taking care of architecture-dependent things) should be handled by underlying infrastructure. Right now I believe our bpm is capable of the task, and my pmake/bpm-fu is strong enough, we'll see. I tried it with patching your Makefile and distinfo. In Makefile I only changed DISTVERSION and DISTNAME and commented out ONLY_FOR_ARCHS. It installs fine and as far as I can see now all is well :-) This is on 9.0-CURRENT (amd64) from today. Rainer Hurling ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nvidia-driver 64bit version
On Fri, Dec 04, 2009 at 03:47:24PM +0100, Emanuel Haupt wrote: > Hi > > I was wondering if you're working on a port for the 64bit version of > the new beta state nvidia driver [1]. Yup, thanks for the pointer. I'm considering options right now. > > Since it's a completely different version it should IMO be separate from > x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver > could be renamed to x11/nvidia-driver-i386. This would be the easiest route, but I'm not sure this is the best thing to do. From user's perspective, one should be able to "cd category/port" and "make install". The rest (including taking care of architecture-dependent things) should be handled by underlying infrastructure. Right now I believe our bpm is capable of the task, and my pmake/bpm-fu is strong enough, we'll see. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
nvidia-driver 64bit version
Hi I was wondering if you're working on a port for the 64bit version of the new beta state nvidia driver [1]. Since it's a completely different version it should IMO be seperate from x11/nvidia-driver. Maybe x11/nvidia-driver-amd64 and x11/nvidia-driver could be renamed to x11/nvidia-driver-i386. Emanuel [1] http://www.nvnews.net/vbulletin/showthread.php?t=142120 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
