From: Florian Engelmann <mailinglists@d-g-c.de>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4fs and SPARC64?
Date: Mon, 21 Feb 2005 15:12:48 +0100 [thread overview]
Message-ID: <4219EC60.5090705@d-g-c.de> (raw)
In-Reply-To: <200502211617.26270.vitaly@namesys.com>
Vitaly Fertman schrieb:
>>libaal-1.0.4.tar.gz compiled fine without any patches.
>>but reiser4progs-1.0.4 did not (also no patches!):
>>
>>
>
>do you have a mix of several installed versions in the system?
>uninstall, check that nothing left and another try will probably help.
>
>
>
you mean of libaal?
no i don't have. I just compiled the kernel today what worked fine (also
i lost my serial console output cause i don't know what drivers i need).
After that i had a look at your ftp and found the new libaal-1.0.4 and
reiser4progs-1.0.4 so i decided to install the newer once. I tried to
patch them with the 2 patches you emaild me but i figured out they are
already patched, aren't they?
The libaal compiled and installed withount any probs but the
reiser4progs didn't.
Should i try to compile 1.0.3? Would reiser4progs 1.0.3 work with libaal
1.0.4???
thx Florian
>>format40.c:255: warning: type defaults to `int' in declaration of `__tmp'
>>format40.c:255: warning: initialization makes integer from pointer
>>without a cast
>>
>>
>
>
>
prev parent reply other threads:[~2005-02-21 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 13:17 Reiser4fs and SPARC64? mailinglists
2005-02-16 14:09 ` Alex Zarochentsev
2005-02-16 14:24 ` Vitaly Fertman
2005-02-17 9:38 ` mailinglists
2005-02-17 9:44 ` Alex Zarochentsev
2005-02-21 12:23 ` mailinglists
2005-02-21 13:44 ` Alex Zarochentsev
2005-02-21 14:13 ` Florian Engelmann
2005-03-02 9:15 ` mailinglists
2005-02-21 12:34 ` mailinglists
2005-02-21 13:17 ` Vitaly Fertman
2005-02-21 14:12 ` Florian Engelmann [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=4219EC60.5090705@d-g-c.de \
--to=mailinglists@d-g-c.de \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.