All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Cc: autofs@linux.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.0.0 beta2
Date: Thu, 18 May 2006 16:56:52 +0200	[thread overview]
Message-ID: <446C8B34.5000602@inria.fr> (raw)
In-Reply-To: <x49mzdfjt3g.fsf@segfault.boston.redhat.com>

Jeff Moyer wrote:
> ==> Regarding Re: [autofs] [ANNOUNCE] autofs 5.0.0 beta2; Guillaume Rousse <Guillaume.Rousse@inria.fr> adds:
> 
> Guillaume.Rousse> I couldn't test it really yet, as mandriva development
> Guillaume.Rousse> kernel is still 2.6.14, however here are a few remarks:
> Guillaume.Rousse> First, stripping binaries by default, especially during
> Guillaume.Rousse> compilation, is opposite behaviour of standard
> Guillaume.Rousse> autotools-based procedure, where it only occurs if you
> Guillaume.Rousse> install with "make stripinstall". I need to have debug
> Guillaume.Rousse> symbols present when building a package, as they are
> Guillaume.Rousse> automatically for extracting them in a separate debug
> Guillaume.Rousse> package. I've found that "make DEBUG=1" would prevent
> Guillaume.Rousse> stripping, but it also defines an additional CFLAG with
> Guillaume.Rousse> unknown result :/
>>> Try the attached patch.  It was made against the 4.1.3 Red Hat packages,
>>> but you get the idea.  Basically, "make -DDONTSTRIP."
> 
> Guillaume.Rousse> I can achieve the same result without the patch with make
> Guillaume.Rousse> CFLAGS="-O2 -g" LDFLAGS="-g" STRIP=":" However, I find a
> Guillaume.Rousse> bit cumbersome to need top pass arguments both to
> Guillaume.Rousse> configure and to make invocation. And I wanted to point
> Guillaume.Rousse> out it was not standard behaviour.
> 
> Well, patches are welcome, I'm sure.  =)
Even one that would replace existing Makefile.in with automake-generated 
ones ? That's the easiest way I know :)

> I've still not gotten to the hesiod patch.  I hope to do it by the end of
> the week.
Don't worry, there is no emergency at all for me, as I still don't have 
the correct kernel to test autofs 5 anyway :/

  reply	other threads:[~2006-05-18 14:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 10:53 [ANNOUNCE] autofs 5.0.0 beta2 Ian Kent
2006-05-10 20:49 ` Guillaume Rousse
2006-05-17  2:45   ` Ian Kent
2006-05-17  2:57     ` Ian Kent
2006-05-18 13:39       ` Guillaume Rousse
2006-05-18 13:38     ` Guillaume Rousse
2006-05-17  3:11   ` Jeff Moyer
2006-05-18 13:39     ` Guillaume Rousse
2006-05-18 14:38       ` Jeff Moyer
2006-05-18 14:56         ` Guillaume Rousse [this message]
2006-05-19 13:31       ` Ian Kent
2006-05-19 13:33         ` Guillaume Rousse
2006-05-20  1:41           ` Ian Kent
2006-05-21 16:51             ` Guillaume Rousse
2006-05-26 22:56     ` Jeff Moyer
2006-05-27  3:08       ` Ian Kent
2006-05-27  8:13       ` Ian Kent
2006-05-27  9:25         ` Ian Kent
2006-05-27 17:26           ` Jeff Moyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446C8B34.5000602@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.