From: Ian Kent <raven@themaw.net>
To: "Philip Ong Jr." <pongjr@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: problem installing 5.0.5
Date: Wed, 27 Jan 2010 10:55:09 +0800 [thread overview]
Message-ID: <4B5FAB0D.4030806@themaw.net> (raw)
In-Reply-To: <4B5E2BE9.8020701@gmail.com>
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.
I don't get this problem here, except that I'm obviously not using
CentOS 4u5.
I tried three times using the 5.0.5 tar, the first by initializing the
source tree as an StGIT repo and importing my local copy of the patches,
second by manually applying my local patches and lastly by wget'ing the
patches from kernel.org and manually applying them.
All makes worked fine.
So your make might be a bit brain dead!
>
> 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?
>
>
> Ian Kent wrote:
>> On 01/22/2010 03:50 PM, Philip Ong Jr. wrote:
>>
>>> When installing 5.0.5 on a Centos 4u5 system with kernel.org 2.6.29.4, i
>>> receive a daemon error.
>>>
>>> Here are the last couple of lines...
>>>
>>> # DEBUG=1 make
>>> gcc -g -Wall -DDEBUG -D_REENTRANT -D_FILE_OFFSET_BITS=64 -rdynamic -fPIE
>>> -D_GNU_SOURCE -I../include -DAUTOFS_LIB_DIR=\"/usr/lib/autofs\"
>>> -DAUTOFS_MAP_DIR=\"/etc\" -DAUTOFS_CONF_DIR=\"/etc/sysconfig\"
>>> -DAUTOFS_FIFO_DIR=\"/var/run\" -DAUTOFS_FLAG_DIR=\"/var/run\"
>>> -DVERSION_STRING=\"5.0.5\" -I/usr/include/libxml2 -c state.c
>>> gcc -g -Wall -DDEBUG -D_REENTRANT -D_FILE_OFFSET_BITS=64 -rdynamic -fPIE
>>> -D_GNU_SOURCE -I../include -DAUTOFS_LIB_DIR=\"/usr/lib/autofs\"
>>> -DAUTOFS_MAP_DIR=\"/etc\" -DAUTOFS_CONF_DIR=\"/etc/sysconfig\"
>>> -DAUTOFS_FIFO_DIR=\"/var/run\" -DAUTOFS_FLAG_DIR=\"/var/run\"
>>> -DVERSION_STRING=\"5.0.5\" -I/usr/include/libxml2 -c flag.c
>>> 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
>>> ../lib/autofs.a(master_tok.o)(.text+0x1b45): In function
>>> `master_set_scan_buffer':
>>> /usr/src/autofs-5.0.5/lib/master_tok.l:417: undefined reference to
>>> `master_lex_destroy'
>>> collect2: ld returned 1 exit status
>>> make[1]: *** [automount] Error 1
>>> make[1]: Leaving directory `/usr/src/autofs-5.0.5/daemon'
>>> make: *** [daemon] Error 2
>>>
>>
>> You need to check on kernel.org for patch updates.
>> This was resolved with patch
>> autofs-5.0.5-dont-use-master_lex_destroy-to-clear-parse-buffer.patch
>>
>> Since the patch changes the CHANGELOG file and there are several other
>> patches before it in patch_order-5.0.5 you will get a rejection unless
>> you also apply the previous patches. I recommend applying all the
>> current 5.0.5 patches (as you would expect).
>>
>> Ian
>>
>>
prev parent reply other threads:[~2010-01-27 2: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.
2010-01-27 3:11 ` Ian Kent
2010-01-28 1:32 ` Philip Ong Jr.
2010-01-27 2:55 ` Ian Kent [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=4B5FAB0D.4030806@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=pongjr@gmail.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.