Folks, Thanks for the education on list etiquete. I will use plain text and avoid the confusing warnings (complained about a specific MIME type when it seems that ANY MIME type is the problem). Based on your guidance I scanned the online manual for autoconfig. This seems to be the source for the terminology in question. In partucular there is a script (config.sub) that is part of the autoconfig toolset that canonicalizes these strings. What seems to be missing is any definition of what each of the field means (cpu, company/manufacturer, os and kernel). The response of config.sub to i386-redhat-linux (i386-redhat-linux-gnu) suggests it (config.sub) is confused too. This would suggest that gnu is an operating system (it is), linux is a kernel (it is), i386 is a cpu (well ...) and redhat is a manufacturer (the aren't - what machines does Redhat produce)? There doesn't seem to be a clear definition on whether "manufacturer" is left or right associative. Most of the other usages suggest it's left associative (binds with CPU rather than OS or OS-Kernel). Anyway - looks like a rather loose notation. Thanks again. Dave Braun BTW I agree with Llwellynn that the result is incorrect but I think the correct answer should be along the lines of i386-pc-linux-gnu (i386-pc indicating a generic i386 platform). There doesn't seem to be any place in the string for a distributor (ala Redhat, Slackware, Suse, etc) even if their OS is a variant. It looks as though the script assumes that the unidentified string "redhat" is an unrecognized hardware manufacture. I tried i386-linux-gnu_redhat and it produced i386-pc-linux-gnu_redhat. i386-gnu_redhat => i386-pc-gnu_redhat. All mildly interesting but useless without a definition. ----- Original Message ----- From: "LLeweLLyn Reese" <llewelly@xxxxxxxxxxxxxxxxxxxxxxxx> To: "Rupert Wood" <me@xxxxxxxxx> Cc: "'David A. Braun'" <braun@xxxxxxxxxxxxxxxxxxxxxx>; <gcc-help@xxxxxxxxxxx> Sent: Monday, August 18, 2003 1:23 PM Subject: Re: GCC Target specification syntax > "Rupert Wood" <me@xxxxxxxxx> writes: > > > David A. Braun wrote: > > > > > Well! That's pretty extreme! Rejecting MIME content type of > > > Text/html! A little paranoid are we? > > > > I don't think it's paranoia - you'll find a lot of free software mailing > > lists object to HTML mail. It's probably historic (lots of free MUAs support > > it fine now) or bandwith or something, or simply some people prefer plain > > text mail anyway. (It gets a mention in the list policies: > > http://gcc.gnu.org/lists.html). If you're still having problems, there's a > > smallish mailing list FAQ here: > > > > http://sources.redhat.com/lists.html > > > > including the anti-spam policies. (IIRC sources.redhat.com is the same > > machine as gcc.gnu.org.) > > > > > At several points in my scan of the GCC installation documentation > > > there are references to target specs such as "i386-redhat-linux" or > > > "alpha*-*-*". Looking at the configure script for several packages > > > there seems to be a standard syntax for this string. Is this syntax > > > documented anywhere? > > > > I've never seen any documentation but the canonical source is the GNU > > 'config' package: config.guess and config.sub. I can't find a homepage for > > it in the FSF software directory and there's no documentation in the config > > CVS beyond comments in the scripts. I've always called it a 'target triple', > > but the format can now be four groups: (from config.sub) > > > > # The goal of this file is to map all the various variations of a > > # given machine specification into a single specification in the > > # form: > > # CPU_TYPE-MANUFACTURER-OPERATING_SYSTEM > > # or in some cases, the newer four-part form: > > # CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM > > # It is wrong to echo any other type of specification. > > Doesn't that imply i386-redhat-linux is either wrong, or implies > redhat is the manufacturer? Should it be i386-pc-linux-redhat ? >
