2009 degrees now available from 55102
[=] You are receiving this m= essage because you submitted the email address po...@freebsd.org to receive in= formation from http://www.directscholar.com on Jun 09 2009 07:25AM. [1]Click here to add us to your address book [2]Ready to go back to school? Search for online + campus-based schools with College.us.com [3]View in Browser | [4]Unsubscribe" style="font-fa= mily:Arial, Helvetica, sans-serif; font-size:10px; color:#000; text-decorat ion:none;">Remove My Email [5]3D"" [6]3D"Want [7]Dear John, Thinking of going back to s= chool? You're in luck. At College.us.com, we've ma= de finding the right school easier than ever. [8]Go to College.us.co= m now. [9]With College.us.com= , you have 3 easy ways to search for schools: 1.Search by Location 2. Search by Category (Area of Study) 3. Search by Program Level Take the next step = toward finding the right school today! [10]Find the right scho= ol now.[college.us=] [11]3D"GO [12][0=] [13]3D"" This email was sent by: = College.us.com 2711 N. Sepulveda Blvd. # 148, Manhattan Beach, CA 90266 You have subsc= ribed to receive information from us with po...@freebsd.org This email was sent to you because you requested we send you periodical inf= ormation about schools and colleges. To stop receiving email from Colle= ge.us.com, [14]Remove me or write us at = the address listed above Please view our [15]Privacy Policy<= /span> [xdbrfmmsm_lrhdfzgfhsh.gif&o=] References Visible links 1. 3D"http://www.n=/ 2. 3D"http://www.news.college.us.com/jtdjtkgst_ 3. 3D"http://www.news.college.us.com/mylfzkqzv_ 4. 3D"http://www.news.college.us=/ 5. 3D"http://www.news.college.us.c=/ 6. 3D"http://www.news.coll=/ 7. 3D"http://www.news.=/ 8. 3D"http://www.news.=/ 9. 3D"http://www.news.=/ 10. 3D"http://www.news.=/ 11. file://localhost/tmp/3D" 12. 3D"http://www.news.college.=/ 13. 3D"http://www.news.coll=/ 14. 3D"http://www.news.college.us.com/vptfmggcz_ 15. 3D"http://www.news.col=/ Hidden links: 16. 3D"http://www.news.college.us.com/fwvrp 17. 3D"http://www.news.college.us.c=/ 18. 3D"http://www.news.college.us.c=/ ___ 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"
Why not use normal CONFLICTS in lang/gcc43 instead of custom?
Hello Gerald, I am trying to install x11/gnome2 last night and the build has gotten stop at lang/gcc43, because of conflict with lang/gcc295. But wait, I don't have lang/gcc295 install. I only have ccache installed that has put 'gcc295' in /usr/local/libexec/ccache/ and this path is in the front of my PATH. It caused lang/gcc43 to find it by mistake. --- # ls -l /usr/local/libexec/ccache/ | grep 295 lrwxr-xr-x 1 root wheel 21 June 12 14:36 g++295@ -> /usr/local/bin/ccache lrwxr-xr-x 1 root wheel 21 June 12 14:36 gcc295@ -> /usr/local/bin/ccache # echo $PATH /usr/local/libexec/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin --- --- pre-extract: @# Building libgcj with lang/gcc295 installed is causing a failure @# about "hidden symbol `__eprintf'" in libgcc.a(_eprintf.o). @if type gcc295 >/dev/null ; then \ echo "This port will not build in the presence of lang/gcc295."; \ exit 1; \ fi --- Puzzled me for you to not use the CONFLICTS, so why not use it? If you really can't use CONFLICTS, then can you use the full path of gcc295? Thanks. Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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: Stop in /usr/ports/lang/gcc43
I am trying to upgrade Ruby, and build Firefox 3.0.11, and they both want to build gcc43 because of gfortran. Really? Firefox needs gfortran to build? I bet not. Anyway, when they try and build gcc43 (of May 31st) on my system, I get into an infinite loop by the pkg system saying that gcc43 requires gfortran to build, that gfortran is not present... the script finally dies. This happens even if I simply do this: cd /usr/ports/lang/gcc43 make It dies there too. So now I cannot upgrade firefox, noway, nohow. Interestingly enough I have gcc44 (with gfortran44!) on the system but these dependencies do not consider that a substitute. I have cvsup'd the ports trees, done portsdb -uF, pkgdb -F, and portupgrade -ar a billion times. It does not help. Everything was fine yesterday, Jun 12th for me. The change came in with Firefox 3.0.11 and some /usr/ports/devel/nspr package that Firefox needs. Something is messed up in the dependencies. Dan Allen ___ 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: [Call For Testing] VirtualBox for FreeBSD! take 6
> on 11/06/2009 22:45 Martin Wilke said the following: >>> - Enable shared OpenGL service. Completely untested due to lack of >>> appropriate hardware but it compiles at least > > Doesn't look like it would work at the run time (at least for me): > OpenGL Error: DLL Loader couldn't find/open /libGL.so.1 > OpenGL Error: The render SPU was unable to load the native OpenGL library > OpenGL Warning: Error closing DLL /libGL.so.1 > > libGL.so.1 lives in /usr/local/lib. To survive while someone fixes vbox, edit /etc/libmap.conf and add something like this : [VirtualBox] /libGL.so.1 /usr/local/lib/libGL.so.1 I had the same problem, and that fixed vbox. And report that shared clipboards with a windows xp guest work for me with virtualbox take 6 ! Thank you ! Greets, Gus > > -- > Andriy Gapon > ___ > freebsd-emulat...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to > "freebsd-emulation-unsubscr...@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: cvs commit: ports MOVED ports/japanese Makefile ports/japanese/slirc Makefile distinfo ports/japanese/slirc/files README.ja patch-editor.sl patch-init.sl patch-lru.c patch-slirc.c patch-vfile-mo
On Sat, Jun 13, 2009 at 07:15:49PM -0400, Philip M. Gollucci wrote: > Erwin Lansing wrote: > > erwin 2009-06-13 14:49:49 UTC > > > > FreeBSD ports repository > > > > Modified files: > > .MOVED > > japanese Makefile > > Removed files: > > japanese/slirc Makefile distinfo > > japanese/slirc/files README.ja patch-editor.sl patch-init.sl > > patch-lru.c patch-slirc.c > > patch-vfile-module.c patch-windoze.c > > Log: > > Remove japanese/slirc. The port has been BROKEN of over 4 months > > and is now also broken against its master port causing a warning > > during INDEX generation. > > horray! > Now stop cheering and start fixing! Today, I went through the ports that were unconditionally BROKEN for more than 3 months, FORBIDDEN, or past their set EXPIRATION_DATE. I plan to do this on a regular basis, so if there is any port you like on these lists, please start sending patches: http://portsmon.freebsd.org/portsconcordanceforforbidden.py http://portsmon.freebsd.org/portsconcordanceforexpiring.py http://portsmon.freebsd.org/portsconcordanceforbroken.py Also, I would like to thank Mark Linimon for creating those reports in portmon and Vasil Dimov for creating the rmport script, without which I wouldn't have been able to do all those commits in one day. -erwin -- Erwin Lansing (o_ _o) http://droso.org \\\_\ /_/// The rest is silence <) (>er...@lansing.dk pgpSPZoYxvSXP.pgp Description: PGP signature
mod_ruby?
Does anyone actually use mod_ruby? Its abandoned upstream and theres this new shiny thing called rails and passenger I hear people seem to like. DEPRCATED/EXPIRES ? ___ 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: Stop in /usr/ports/lang/gcc43
>I am trying to upgrade Ruby, and build Firefox 3.0.11, and they both >want to build gcc43 because of gfortran. Really? Firefox needs >gfortran to build? I bet not. I bet not, too. I took a cursory look through my ports tree, and the recent changes, and I can't see how such a dependency was introduced. I think something is wrong with your system. Of course, if you were using www/firefox3-devel on FreeBSD 6.x, that's another matter -- there, you could get the dependency chain: audio/pulseaudio --> audio/libsamplerate --> math/fftw3 , the last of which had a new Fortran dependency introduced recently. But ruby? I can't think of how this happened. I don't see any recent change to firefox3 or nspr that could have led to this. >Anyway, when they try and build gcc43 (of May 31st) on my system, I >get into an infinite loop by the pkg system saying that gcc43 requires >gfortran to build, that gfortran is not present... the script finally >dies. >This happens even if I simply do this: cd /usr/ports/lang/gcc43 make >It dies there too. So now I cannot upgrade firefox, noway, nohow. Some care is taken to avoid introducing circular dependencies in Ports, so this shouldn't happen. It sounds to me as if you have mistakenly introduced a USE_FORTRAN=yes into your build environment somehow. What does:"env | grep FORTRAN" and "grep -e 'FORTRAN' /etc/make.conf" give you? How about "make -C /usr/ports/lang/gcc43 -V USE_FORTRAN" ? Normally, they should all be empty. >Interestingly enough I have gcc44 (with gfortran44!) on the system but >these dependencies do not consider that a substitute. If USE_FORTRAN=yes, the Ports build infrastructure will only try to find gfortran43. See /usr/ports/Mk/bsd.gcc.mk >I have cvsup'd the ports trees, done portsdb -uF, pkgdb -F, and >portupgrade -ar a billion times. It does not help. Everything was >fine yesterday, Jun 12th for me. The change came in with Firefox >3.0.11 and some /usr/ports/devel/nspr package that Firefox needs. >Something is messed up in the dependencies. Indeed. If you hadn't reported the problem with a simple 'make', but only when using portupgrade, I would have suspected a corrupt pkgdb, in which case I would have recommended rebuilding it with pkgdb -L. But something else seems to be wrong here. Maybe the information in /var/db/pkg is bad? You might try removing your ports tree, and then using a completely fresh tree obtained from a tarball or from portsnap, with a new INDEX. If this doesn't work, you could try removing and then rebuilding all of your ports. But check to see that you don't have a stray USE_FORTRAN in your environment, first. And when you do builds, run "make clean" or "portsclean -C" first, so that you're not restarting a stale build. b. ___ 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"
