![]() (and over 150 more symbols that didn't fit)Ī google search turned up some forum posts, a blog post, and an article on the AMD64 ABI support in the Sun Studio compilers. Ld: fatal: relocation error: R_AMD64_PC32: file decode11.o: symbol LBXEvent: value 0x808664c3 does not fit Ld: fatal: relocation error: R_AMD64_PC32: file audio.o: symbol ServerHostName: value 0x8086b4fe does not fit Ld: fatal: relocation error: R_AMD64_PC32: file audio.o: symbol littleEndian: value 0x8086c355 does not fit The builds run fine up until the final link stage, which fails Up in the 64-bit builds of the xscope protocol monitor/decoder for X11 on (Ideally I'd set up a Solaris clientĪnyways, recently I finally decided to track down an error that only shows Helps me catch issues that would break our builds when we integrate the new On the latest Solaris 11 internal development build, but I also occasionallyĭo it in 64-bit mode, or with gcc compilers, or on a SPARC machine. Normally I do this in 32-bit mode on x86 machines using the Sun compilers Modules from X.Org (at least all those listed in the current build.sh) on Solaris. I try to fairly regularly build recent git checkouts of all the upstream Be warned that if you switch screens at runtime, you also want to apply the patch from bug #645408 for now. After getting that to work, I couldn’t resist writing an extension to do it for me. So after a little messing around with Looking Glass (which is pretty amazing), I was able to set the variable into the shell and have it re-exec itself. Luckily NVidia (yea sorry) has an environment variable to select which monitor an OpenGL application syncs on, the annoying thing is that this has to be set before the application is started. ![]() So when I have two monitors, I want the VSync to be on the second monitor. ![]() How incredible is that! The thing is, my second monitor is a 50″ Plasma TV and I really hate tearing there when I watch a movie. That said, we’re in 2011, and it’s still impossible to use OpenGL on two monitors without tearing. It is definitely going in the right direction. Yes, it has a few annoying bugs and glitches, but nothing out of the ordinary for a first release. Tagged: communication, community, gentoo, gsocĪfter months of envy, I decided that since GNOME 3 is to be released in almost two weeks, it was time to try it out. Remember that you’re part of a community.Ĭonsider it a solo project, like it often is in college. Make Google Summer of Code your top priority.Ĭommit and publicize your code frequently.įinish the summer with code that’s “almost ready” but will take forever to ship.Ĭomplete your project design before writing a line of code. Read all the documentation, so you submit a useful application. Make a bad first impression: SMS speech, extremely poor English, rudeness/hostility, etc. Here’s a quick summary of the points you’ll have to read the original post for details: DO They’re fellow admins from two other long-time GSoC participants, KDE and the XMPP Standards Foundation. I’d like to point any potential Google Summer of Code applicants to a post on DOs and DON’Ts for students over on the Google Open Source blog that I wrote with Lydia Pintscher and Kevin Smith.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |