All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince <fuzzy77@free.fr>
To: David Nielsen <Lovechild@foolclan.com>
Cc: reiserfs-list@namesys.com
Subject: Re: New reiser4 snapshot (as of August 22, 2003)
Date: Sat, 23 Aug 2003 02:25:59 +0200	[thread overview]
Message-ID: <3F46B497.60106@free.fr> (raw)
In-Reply-To: <1061596035.21328.10.camel@pilot.stavtrup-st.dk>

I worked around this by adding an empty info_atom in reiser4/txnmgr.c :

void
info_atom(const char *prefix, txn_atom * atom)
{
         return;
}

  After that, reiser4 compiles and is running without problem here so 
far (just tried a few minutes of fsx-linux and a few small compilations. 
I'll launch a mozilla-firebird build soon and see if it survives better 
this time).

BTW : compilation as a module is still broken for me, but it could be my 
fault as I'm using an -mm kernel...
(For information, missing symbols are: max_sane_readahead, 
generic_sync_sb_inodes, truncate_mapping_pages_range, 
balance_dirty_pages_ratelimited, inodes_stat, nr_free_pagecache_pages, 
get_full_page_state, destroy_inode)

Sidenote to reiserfs devels : if the merge in mainstream is still far 
away, is any integration of reiser4 into the -mm serie considered ? It 
would ease testing a lot...

Vincent

David Nielsen wrote:
> The entire thing then fails with these messages - no notable compile
> errors or warnings present. 
> 
> fs/built-in.o(.text+0x9a8cd): In function `print_context':
> : undefined reference to `info_atom'
> fs/built-in.o(.text+0x9e392): In function `commit_current_atom':
> : undefined reference to `info_atom'
> fs/built-in.o(.text+0xa0577): In function `print_atom':
> : undefined reference to `info_atom'
> make: *** [.tmp_vmlinux1] Error 1
> 
> Seems this patch might have benefited from a compile test at least? :)
> 
> regards David
> 
> 



  parent reply	other threads:[~2003-08-23  0:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22 15:08 New reiser4 snapshot (as of August 22, 2003) Oleg Drokin
2003-08-22 17:52 ` David Nielsen
2003-08-22 17:57   ` Nikita Danilov
2003-08-22 18:08     ` David Nielsen
2003-08-22 18:12       ` Nikita Danilov
2003-08-22 23:47         ` David Nielsen
2003-08-23  0:15           ` Christophe Saout
2003-08-23  0:25           ` Vince [this message]
2003-08-23  0:29             ` David Nielsen
2003-08-23  3:38             ` Boris Tschirschwitz
2003-08-23  1:57           ` Hans Reiser
2003-08-23  1:16 ` Tupshin Harper
2003-08-23  3:07   ` Jürgen Botz
2003-08-23  7:39   ` Oleg Drokin
2003-08-23  8:06 ` David Nielsen

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=3F46B497.60106@free.fr \
    --to=fuzzy77@free.fr \
    --cc=Lovechild@foolclan.com \
    --cc=reiserfs-list@namesys.com \
    /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.