[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: target triplet
From: |
Bob Rossi |
Subject: |
Re: target triplet |
Date: |
Sun, 21 Jan 2007 17:44:24 -0500 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
On Sun, Jan 21, 2007 at 11:22:40PM +0100, Ralf Wildenhues wrote:
> Hello Bob,
>
> * Bob Rossi wrote on Sun, Jan 21, 2007 at 11:15:23PM CET:
> >
> > I would like to get access to the target triplet fields. The cpu, os
> > and vendor strings. Does autoconf provide these separatly?
>
> Here you go:
> <http://www.gnu.org/software/autoconf/manual/html_node/Canonicalizing.html>
>
> > If not, what's the correct way to parse it? Would it be,
> > cpu-os-vendor, where os could contain a - but cpu and vendor may not?
>
> Correct.
>
> But if you're out to use them as deciding data in configure tests, be
> reminded that leaving behind feature-based tests is the path that leads
> to the Dark Side. The maintenance costs may haunt you in the long run.
Sure, I need to know what path separator to use in my application.
I also need to know what separator to use in environment variables. Do
you have any better ideas than testing for mingw or cygwin?
Thanks,
Bob Rossi
- Re: target triplet, Steven G. Johnson, 2007/01/03
- target triplet, Bob Rossi, 2007/01/21
- Re: target triplet, Ralf Wildenhues, 2007/01/21
- Re: target triplet,
Bob Rossi <=
- Re: target triplet, Brian Dessent, 2007/01/21
- Re: target triplet, Ralf Wildenhues, 2007/01/21
- Re: target triplet, Keith MARSHALL, 2007/01/22
- path separator (was: target triplet), Ralf Wildenhues, 2007/01/22
- Re: path separator (was: target triplet), Bob Rossi, 2007/01/22
- Re: path separator (was: target triplet), Keith MARSHALL, 2007/01/23
- Re: path separator (was: target triplet), Matthew Woehlke, 2007/01/23
- Re: path separator (was: target triplet), Keith MARSHALL, 2007/01/23
- Re: path separator (was: target triplet), Matthew Woehlke, 2007/01/23
- Re: path separator (was: target triplet), Brian Dessent, 2007/01/23