nanogui: freetype 1.3.1
Subject:
Re: freetype 1.3.1
From:
"Jordan Crouse" ####@####.####
Date:
11 Nov 2005 16:57:29 +0000
Message-Id: <20051111165930.GA761@cosmic.amd.com>
On 11/11/05 10:57 -0500, Gil Glass wrote:
> Incidentally, the proposed solution below of setting the "sizeof"
> variable(s) in the command line does solve the problem of assigning the
> value(s) but won't the pesky configure script still complain that it can't
> build the test program(s)? Or is it smart enough to know not to do that
> if that part has already been configured?
Yeah - it works like a cache in that regard. Is as_sizeof_char set? Ok,
well then I won't try to build to test it.
Jordan
> Gil Glass
> Telecom Field Services
> JDSU
> Germantown, MD, USA
> +1-240-404-2551
>
>
>
>
> "Jordan Crouse" ####@####.####
> 11/10/2005 12:32 PM
>
> To
> "Peter Barada" ####@####.####
> cc
> ####@####.#### ####@####.#### ####@####.####
> Subject
> Re: freetype 1.3.1
>
>
>
>
>
>
> On 10/11/05 10:01 -0500, Peter Barada wrote:
> >
> > >I'm not familiar with the config.cache solution. What I did in this
> exact
> > >same circumstance was to manually modify the config file to
> >
> > You could try instead to supplie a value of ac_cv_sizeof_int in the
> > environment when you invoke configure, as in:
> >
> > ac_cv_sizeof_int=4 /path/to/configure --target=...
>
> Doing this or the config.cache solution is far preferred to editing the
> configure file - thats a bad habit to get into... :)
>
> Jordan
>
> > --
> > Peter Barada
> > ####@####.####
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.####
> > For additional commands, e-mail: ####@####.####
> >
> >
>
> --
> Jordan Crouse
> Senior Linux Engineer
> AMD - Personal Connectivity Solutions Group
> <www.amd.com/embeddedprocessors>
>
>
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
