Hello, Peter. You wrote 8 апреля 2012 г., 16:04:46: > mspgcc doesn't do this intentionally. AFAIK, the only thing the > patches do about pic is disable it (with a warning) if it's passed to > the gcc driver. It seems, that something changed between gcc 4.5 and 4.6 mainstream itself. FreeBSD like to be "amd64" and GNU people like to name it "x86_64". gcc 4.5 configures itself properly without additional hacks, and gcc 4.6 needs `--build=x86_64-blah-blah-blah' (instead of "canonical" for FreeBSD `--build=amd64-blah-blah-blah') argument to configure itself properly.
So, problem is solved and FreeBSd ports will be updated today to latest & greatest LTS release. -- // Black Lion AKA Lev Serebryakov <l...@serebryakov.spb.ru> ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
