From: "Philip Ong Jr." <pongjr@gmail.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: problem installing 5.0.5
Date: Tue, 26 Jan 2010 11:55:35 -0800 [thread overview]
Message-ID: <4B5F48B7.2010002@gmail.com> (raw)
In-Reply-To: <4B5EFB4D.9080808@themaw.net>
I have not, how do I go about doing that?
Phil
Ian Kent wrote:
> On 01/26/2010 07:40 AM, Philip Ong Jr. wrote:
>
>> I applied the patches starting from top to down...and now receiving
>> error messages pertaining to conditional statements.
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-included-map-read-fail-handling.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-refactor-ldap-sasl-bind.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.4-add-mount-wait-parameter.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-special-case-cifs-escapes.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-libxml2-workaround-configure.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-more-code-analysis-corrections.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-backwards-ifndef-INET6.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-stale-init-for-file-map-instance.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-ext4-fsck-at-mount.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-dont-use-master_lex_destroy-to-clear-parse-buffer.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-make-documentation-for-set-log-priority-clearer.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-timeout-in-connect_nb.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-pidof-init-script-usage.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-check-for-path-mount-location-in-generic-module.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-dont-fail-mount-on-access-fail.patch
>>
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-rpc-large-export-list.patch
>> patch -p1 <
>> /usr/src/autofs-5.0.5/patches/autofs-5.0.5-fix-memory-leak-on-reload.patch
>>
>> # ./configure --disable-mount-locking --enable-ignore-busy
>>
>> # DEBUG=1 make
>>
>> gcc -g -lpthread -rdynamic -pie -o automount automount.o indirect.o
>> direct.o spawn.o module.o mount.o lookup.o state.o flag.o
>> ../lib/autofs.a -ldl -lxml2 -lz -lpthread -lm
>> : automount
>> make[1]: Leaving directory `/usr/src/autofs-5.0.5/daemon'
>> make[1]: Entering directory `/usr/src/autofs-5.0.5/modules'
>> Makefile:75: Extraneous text after `else' directive
>> Makefile:80: Extraneous text after `else' directive
>> Makefile:80: *** only one `else' per conditional. Stop.
>> make[1]: Leaving directory `/usr/src/autofs-5.0.5/modules'
>> make: *** [daemon] Error 2
>>
>> Thoughts?
>>
>
> Oh ... bummer, wonder how I've broken the patch series?
>
> I'll check it out and get back to you.
> In the meantime, have you tried checking out the git repo and building that?
>
> Ian
>
>
next prev parent reply other threads:[~2010-01-26 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 7:50 problem installing 5.0.5 Philip Ong Jr.
2010-01-25 3:28 ` Ian Kent
2010-01-25 23:40 ` Philip Ong Jr.
2010-01-26 14:25 ` Ian Kent
2010-01-26 19:55 ` Philip Ong Jr. [this message]
2010-01-27 3:11 ` Ian Kent
2010-01-28 1:32 ` Philip Ong Jr.
2010-01-27 2:55 ` Ian Kent
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=4B5F48B7.2010002@gmail.com \
--to=pongjr@gmail.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/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.