From: Ian Kent <raven@themaw.net>
To: Nail El-Sourani <sourani@math.uni-muenster.de>
Cc: "'autofs@linux.kernel.org'" <autofs@linux.kernel.org>
Subject: Re: 5.0.4 with all patches -> compile error on 64bit
Date: Fri, 05 Jun 2009 10:04:47 +0800 [thread overview]
Message-ID: <4A287D3F.70808@themaw.net> (raw)
In-Reply-To: <4A2879A2.9010101@themaw.net>
Ian Kent wrote:
>> ...
>> gcc -O2 -Wall -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.4\" -c flag.c
>> gcc -s -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
>> ../lib/autofs.a(master_tok.o): In function `master_set_scan_buffer':
>> master_tok.c:(.text+0x257): undefined reference to `master_lex_destroy'
>> collect2: ld gab 1 als Ende-Status zurück
>> make[1]: *** [automount] Fehler 1
>> make[1]: Leaving directory `/root/Desktop/autofs-5.0.4/daemon'
>> make: *** [daemon] Fehler 2
>>
>>
>> (these are the last few lines)
>>
>> i am suspecting a problem with 64bit but then again, what do i know...
>> this is a centos5.3 64bit machine
>
> OK I'll fix that.
> I think it's the Lexx version what is too old.
But then again maybe not, the flex version is just to old, I'm not sure
that the bleeding edge upstream source should make compromises for older
flex versions. The function master_lex_destroy() (actually yy... since
this is a multiple parser lexer) does more than just clear the user
parse buffer, and the 5.0.4 patch does a couple of other things as well.
A configure change and some #ifdef ugliness might do the trick I guess.
Not looking forward to doing that!
Ian
prev parent reply other threads:[~2009-06-05 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 8:56 5.0.4 with all patches -> compile error on 64bit Nail El-Sourani
2009-06-05 1:49 ` Ian Kent
2009-06-05 2:04 ` 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=4A287D3F.70808@themaw.net \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=sourani@math.uni-muenster.de \
/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.