nanogui: freetype 1.3.1
Subject:
Re: freetype 1.3.1
From:
Gil Glass ####@####.####
Date:
11 Nov 2005 15:59:19 +0000
Message-Id: <OF0A7D6471.2DF37549-ON852570B6.005755DD-852570B6.0057B2C2@acterna.com>
Agreed! It's a terrible habit but one that some of the harder-core
hackers in my company, of which I am not by the way, are mostly in.
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?
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>
