All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: mktree.c does not compile with v14 ?
Date: Tue, 31 Mar 2009 11:08:27 -0400	[thread overview]
Message-ID: <49D231EB.90706@cs.columbia.edu> (raw)
In-Reply-To: <20090331005703.GA19223-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


Yes, the version I uploaded was broken :(
Please try v14-rc2 from the same tree.

Oren.

Sukadev Bhattiprolu wrote:
> I am trying to compile mktree.c with [v14-rc1] but get this:
> 
> $ make mktree
> cc -g -Wall -Wstrict-prototypes -Wno-trigraphs -I/home/suka/src/linux-cr/include -I/home/suka/src/linux-cr/arch/x86/include -DCHECKPOINT_DEBUG    mktree.c  -lm -o mktree
> mktree.c: In function ‘cr_read_head’:
> mktree.c:563: error: ‘struct cr_hdr_head’ has no member named ‘uts_len’
> mktree.c: In function ‘cr_write_head’:
> mktree.c:639: error: ‘struct cr_hdr_head’ has no member named ‘uts_len’
> make: *** [mktree] Error 1
> 
> The kernel cr_hdr_head has members ->uts_release_len, ->uts_version_len,
> ->uts_machine_len but no ->uts_len
> 
> Thanks,
> 
> Sukadev
> 
> 
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

      parent reply	other threads:[~2009-03-31 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  0:57 mktree.c does not compile with v14 ? Sukadev Bhattiprolu
     [not found] ` <20090331005703.GA19223-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-31  1:47   ` Dan Smith
2009-03-31 15:08   ` Oren Laadan [this message]

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=49D231EB.90706@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 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.