From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] problem with dump
Date: Sun, 04 Sep 2011 18:21:04 -0400 [thread overview]
Message-ID: <yu91uvwdk4v.fsf@nyu.edu> (raw)
I noticed that the last two (daily) dumps have been bad (too short,
unreadable by restore).
I tried to remerge app-arch/dump both 0.4.44-r1 (which I had before)
and o.4.44. Both failed in the compile phase (details below).
This seem a little frightening to me. Can someone tell me what has
happened
thanks,
allan
system is ~amd64. The filesystem is ext3
x86_64-pc-linux-gnu-gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -march=native -O2 -pipe -ggdb -pipe -I.. -I../compat/include -I/usr/include/ext2fs -I/usr/include/et -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b44\" traverse.c -o traverse.o
x86_64-pc-linux-gnu-gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL -march=native -O2 -pipe -ggdb -pipe -I.. -I../compat/include -I/usr/include/ext2fs -I/usr/include/et -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO -D_PATH_DUMPDATES=\"/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b44\" unctime.c -o unctime.o
sed -e "s|__DUMPDATES__|/etc/dumpdates|g" \
-e "s|__DATE__|June 10, 2011|g" \
-e "s|__VERSION__|0.4b44|g" dump.8.in > dump.8
traverse.c: In function ‘dumpino’:
traverse.c:1000:49: error: ‘struct struct_ext2_filsys’ has no member named ‘fragsize’
traverse.c:1001:58: error: ‘struct struct_ext2_filsys’ has no member named ‘fragsize’
traverse.c:1002:24: error: ‘struct struct_ext2_filsys’ has no member named ‘fragsize’
traverse.c:1002:24: error: ‘struct struct_ext2_filsys’ has no member named ‘fragsize’
traverse.c: In function ‘blksout’:
traverse.c:1277:9: error: ‘struct struct_ext2_filsys’ has no member named ‘fragsize’
make[1]: *** [traverse.o] Error 1
next reply other threads:[~2011-09-04 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 22:21 Allan Gottlieb [this message]
2011-09-04 22:48 ` [gentoo-user] problem with dump Alex Schuster
2011-09-04 23:16 ` Allan Gottlieb
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=yu91uvwdk4v.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--cc=gentoo-user@lists.gentoo.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