Hi all,
I was struggling with some AC_ARG_ENABLE stuff in my project today.
Seems like some people have done ./configure --enable-foo when the
AC_ARG_ENABLE code was as follows: (simplified)
AC_ARG_ENABLE(foo
AC_HELP_STRING([--disable-foo], [Disable the usage of foo]),
[AC_DEFINE(USE_FOO, 1, bl
Hockey Arena Product As Important As The Ice
EdgerClick To Learn More & See Product
Movie
Product
announcements, arena industry news, safety alerts, and free promotional
activities provided by[EMAIL PROTECTED] you would like to
be removed f
Look Younger and Lose Weight in 3 Weeks
The health discovery that reverses signs of aging naturally and that is completely safe and effective is on sale for a limited time! Buy a two-month supply of our product and we will give you one month free!
Click here
f
Jim Meyering wrote:
Regarding this:
http://mail.gnu.org/archive/html/bug-gnulib/2003-05/msg00014.html
[. . . snip . . .]
Do you know if it'd solve the problem to make the prerequisite tests
unconditional?
Yes, it would.
I really hope so, because using cache variable names
from other tests m
Regarding this:
http://mail.gnu.org/archive/html/bug-gnulib/2003-05/msg00014.html
Derek Robert Price <[EMAIL PROTECTED]> wrote:
> I've attached a patch for the lstat half of the stat replacements.
>
> The main problem this addresses is that on systems where lstat has
> problems with trailing sl
On Tue, Jun 10, 2003 at 05:55:21PM +0200, Andreas Schwab wrote:
> Remko Troncon <[EMAIL PROTECTED]> writes:
> |> Am
> |> i right if stripping a binary compiled with -g is not the same thing as
> |> not compiling it with -g ?
>
> $ strip -g
Which is itself nonportable. On Solaris 7, the closeest
Also sprach Remko Troncon:
} > export CFLAGS=whatever
}
} Of course, but then i overwrite all flags that configure sets by
} default, and that's probably not very clean (although i don't think it
} makes a lot of difference at this point).
}
We have the same problem with our library. I use a home
On Tue, Jun 10, 2003 at 05:10:23PM +0200, Andreas Schwab wrote:
> Remko Troncon <[EMAIL PROTECTED]> writes:
>
> |> Hi,
> |>
> |> I was wondering why the standard CFLAGS for configure are chosen to be
> |> -g -O2 ? Is there a clean way to remove the '-g' from these flags, to
>
> export CFLAGS=wha
Remko Troncon <[EMAIL PROTECTED]> writes:
|> That was the wrong word. I meant 'a binary, without debugging code'. Am
|> i right if stripping a binary compiled with -g is not the same thing as
|> not compiling it with -g ?
$ strip -g
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE
Remko Troncon <[EMAIL PROTECTED]> writes:
|> Hi,
|>
|> I was wondering why the standard CFLAGS for configure are chosen to be
|> -g -O2 ? Is there a clean way to remove the '-g' from these flags, to
export CFLAGS=whatever
|> have configure build a distributable binary by default ?
What do you
> export CFLAGS=whatever
Of course, but then i overwrite all flags that configure sets by
default, and that's probably not very clean (although i don't think it
makes a lot of difference at this point).
> |> have configure build a distributable binary by default ?
> What do you mean with "distrib
Hi,
I was wondering why the standard CFLAGS for configure are chosen to be
-g -O2 ? Is there a clean way to remove the '-g' from these flags, to
have configure build a distributable binary by default ?
thanks,
Remko
12 matches
Mail list logo
