> I was assuming that you were running 4.3.0. Eric A. is the maintainer > for the FreeBSD port, but he is trying to get 4.3.0 out for the 4.8 > release, so he is probably not interested in 4.2 patches any longer.
ok. to clarify, I'm running 4.2.1 on freebsd 4.8-RC, all sw is latest released -STABLE tree as of yesterday. and my last mail said pkg. I didn't mean that. I mean strictly by ports (src) only, at my site. > > If you built from ports, you should have 4.2.1 which I run on a dual > head Matrox with no problems. (In fact, I am using it to send this > message.) I use portupgrade to keep my ports up to date and use the > '-DWITH_MATROX_GXX_DRIVER' option to make by entering it into yes, I forced that define! I know that since I did a 'file' on the .o matrox hal files and they said freebsd. if you do a file on them ON a bsd box and they are the 'linux' (matrox built .o files) they simply don't say freebsd in parens. so I know I built them ok with that define, like you said. hmmm. wonder why it didn't work for me. are you using dual dvi, which REQUIRES hal_lib ? > /usr/local/etc/pkgtools.conf. It builds with the sources in > mgadrivers-2.0-src.tgz. I don't see why your results were different. well, they are. I could swap back to the bsd-built mga_foo.o files and I bet dualhead won't work (even singlehead didn't work). then I swap in the linux .o files and all is fine. > > Eric A. is the maintainer for the FreeBSD port, but he is trying to get > 4.3.0 out for the 4.8 release, so he is probably NOT interested in 4.2 > patches any longer. well, 4.3 is fine. I just wanted to be able to build the port and run my workstation on bsd instead of linux. trying to migrate all away from linux but it was a very frustrating day yesterday. took the entire day to get bsd X to work. only takes a few hrs (at most) to do that on linux (sigh..) > > > > > > > > > When you referred to the mga_drv.o in ports, did you really mean the > > > package? The port should fetch the same Matrox sources that you used and > > > build them. > > > > I mean pkg. I build all things from src on my own machine, I never use > pkgs, > > only ports. > > > > the SOURCE is being fetched and the _drv.o files are being created, > > but they don't work! only the pre-built matrox .o files from their > > site, being slammed into the right lib/.../modules area works. weird, > > huh? > > Very weird! I am baffled as to why your results are different. It is > nice that the XFree86 driver binaries are OS independent so that they > work on both Linux and FreeBSD. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 > > ===== (please ignore any YAHOO trailers in this email.) __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
