Linux Container Development
 help / color / mirror / Atom feed
From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] Enhance checkpoint/restart Kconfig options
Date: Fri, 05 Jun 2009 12:01:00 -0700	[thread overview]
Message-ID: <1244228460.12947.3185.camel@nimitz> (raw)
In-Reply-To: <m2zlcnfgst.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>

On Thu, 2009-06-04 at 23:25 -0500, Nathan Lynch wrote:
> > Ahh, but there *isn't* a strict build dependency on them.  We just
> want
> > to make sure that if they're available that we enable them.  If we
> have
> > CONFIG_NET=n, then we certainly don't want to make CHECKPOINT
> depends on
> > it.
> 
> Sorry, I'm afraid I don't understand what you're saying here.
> 
> Here's a concrete example of what I'm talking about.
> 
> $ git checkout oren/ckpt-v16
> $ make ARCH=i386 i386_defconfig
> [ edit .config, enable CONFIG_CHECKPOINT and disable CONFIG_NET ]
> $ make ARCH=i386 -s vmlinux   # which should succeed
> [ apply your patch ]
> $ make ARCH=i386 -s vmlinux
> kernel/built-in.o: In function `free_nsproxy':
> (.text+0x1daaf): undefined reference to `__put_net'
> make: *** [.tmp_vmlinux1] Error 1

Kconfig is almost as retarded as me. :)  Thanks for the cluebat.

-- Dave

  parent reply	other threads:[~2009-06-05 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090604184504.F1BCB2F8@kernel>
2009-06-04 20:01 ` [PATCH] Enhance checkpoint/restart Kconfig options Nathan Lynch
     [not found]   ` <m3iqjbix8u.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-04 20:17     ` Dave Hansen
2009-06-05  1:32       ` Oren Laadan
2009-06-05  4:25       ` Nathan Lynch
     [not found]         ` <m2zlcnfgst.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2009-06-05 19:01           ` Dave Hansen [this message]
2009-06-04 20:41 ` Serge E. Hallyn

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=1244228460.12947.3185.camel@nimitz \
    --to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox