The "triplet" (or "quad") i386-pc-solaris2.11 is ambiguous.
Try a bit of Googling for i386-pc-solaris2.11 : http://www.google.com/search?q=i386-pc-solaris2.11&rls=com.microsoft:en-us:IE-SearchBox&ie=UTF-8&oe=UTF-8&sourceid=ie7&rlz=1I7HPIA The first hit: sang-suan gam - Results for 4.2.2 testsuite on i386-pc-solaris2.11 http://www.google.com/url?sa=U&start=1&q=http://gcc.gnu.org/ml/gcc-testresults/2007-11/msg00285.html&ei=zCBnSfjzEIG0sAOzmsyKAw&usg=AFQjCNGRgG2yLcUybRMk5v0upqQiVZJRBQ Reporter "sang-suan gam" claims his(?) i386-pc-solaris2.11 is: "Solaris Express Developer Edition 9/07 snv_70b X86" The second hit: Dennis Clarke - gcc 4.2.2 bootstrap fails on i386-pc-solaris2.1113 http://www.google.com/url?sa=U&start=2&q=http://gcc.gnu.org/ml/gcc-help/2007-10/msg00158.html&ei=zCBnSfjzEIG0sAOzmsyKAw&usg=AFQjCNENSCHBmDp3gP62JQ51_Jx4CU_slw Reporter "Dennis Clarke" claims his i386-pc-solaris2.11 is (follow link): "$ uname -a SunOS aequitas 5.11 snv_69 i86pc i386 i86pc" My Operating System is "OpenSolaris 2008.11" and my identifier is also i386-pc-solaris2.11 but my kernel version is 30 revisions newer. That makes a huge difference. Your getting the ".11" from the 5.11 and ignoring the next field which is also important. In a year "Solaris 11" will be using the same identifier, ( i386-pc-solaris2.11 ), as Solarises from over a year ago (with sidderent names). Just prior to changing to a new one, OpenSolaris wiil still use that identifier a year from now. The identifier i386-pc-solaris2.11 can apply to these Operating Systems: 1. Solaris Express Developer Edition 2. Solaris Express Community Edition 3. Solaris 11 (not yet released - just a guess) 4. OpenSolaris 2008.05 (With updates applied) 5. OpenSolaris 2008.11 6. OpenSolaris 2009.05 (not yet released - just a guess) Here is my uname: # uname -a SunOS opensolaris 5.11 snv_101b i86pc i386 i86pc If you check the testsuite reports you can see wildly varying results for platform i386-pc-solaris2.11 (and various names for the _actual_ Operating System (on those occasions when people thought to write the info)). Some of the differences are due to different ".h" files and different programs that are installed leading ./configure to 'discover' differing features on the different platforms that all identify themselves as: i386-pc-solaris2.11 In the above three examples your could barely get away with calling the platforms the following instead: i386-pc-solaris2.11.70b i386-pc-solaris2.11.69 i386-pc-solaris2.11.101b That is not guaranteed to work 100% and the day could come when we get hit but it is extremely likely to be OK and not cause any ambiguity. Thanks, Rob -- Summary: [Regression] - The "triplet" i386-pc-solaris2.11 is ambiguous Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: other AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: rob1weld at aol dot com GCC build triplet: i386-pc-solaris2.11 GCC host triplet: i386-pc-solaris2.11 GCC target triplet: i386-pc-solaris2.11 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38783
