[Memchan-track] [ memchan-Bugs-1080325 ] Cannot build memchan 2.2.1

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Bugs item #1080325, was opened at 2004-12-06 23:45
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410295&aid=1080325&group_id=34191

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 60. other
Group: None
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Joe English (jenglish)
Assigned to: Pat Thoyts (patthoyts)
Summary: Cannot build memchan 2.2.1

Initial Comment:
Environment: Mandrake Linux 10.0,  Tcl 8.5 (recentish
CVS HEAD) installed in /usr/local.

Take 1:
$ tar xzf memchan-2.2.1.tar.gz
$ cd memchan-2.2.1
$ sh configure
[ ... configure output elided ...]
$ make
make: *** No rule to make target `memchanStubInit.o',
needed by `libMemchan2.2.1.so'.  Stop.

Take 2:
$ tar xzf memchan-2.2.1.tar.gz
$ cd memchan-2.2.1/unix
$ sh configure
[ ... configure output elided ...]
$ make
[ ... this succeeds, creating libmemchan.so, but: ...]
$ tclsh
% load ./libmemchan.so
couldn't load file "./libmemchan.so": ./libmemchan.so:
undefined symbol: memchanStubs

Take 3:
$ tar xzf memchan-2.2.1.tar.gz
$ cd memchan-2.2.1/unix
$ sh ../configure
[ ... ]
$ make
make: *** No rule to make target
`../../generic/init.c', needed by `init.o'.  Stop.

Take 4:
$ tar xzf memchan-2.2.1.tar.gz
$ mkdir /tmp/build
$ cd /tmp/build
$ sh ~/dl/memchan-2.2.1/configure
[...]
$ make
[ This finally worked.  I'm afraid to run 'make
install' though.]

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-03-15 22:07

Message:
I still get basically the same results as before:

$ tar xzf memchan-2.2.1.tar.gz
$ cd memchan-2.2.1
$ sh configure
[...]
make: *** No rule to make target `memchan.o', needed by
`libMemchan2.2.1.so'.  Stop.

(and similarly for the other approaches).

Recommend closing once a newer release is available.

----------------------------------------------------------------------

Comment By: Stuart Cassoff (stwo)
Date: 2009-03-15 17:56

Message:
This works now for me, with the exception of building the documentation,
which is a separate issue, imho.
Recommend closing.

----------------------------------------------------------------------

Comment By: Pat Thoyts (patthoyts)
Date: 2004-12-08 11:11

Message:
Logged In: YES 
user_id=202636

I'll take a look at this. Memchan should be TEA 3 compliant
and this means the toplevel configure/makefile.in. The stuff
in unix/ probably should be removed but that's for Andreas
to decide as it's all pre8.2 compatability stuff. 

Same goes for the old win buld files. Can we clean up the
old junk?

If the toplevel files don't do the expected TEA things then
they need fixing. Worked for me, but I always create a
subdirectory to build in. I shall try without.

----------------------------------------------------------------------

Comment By: Andreas Kupries (andreas_kupries)
Date: 2004-12-07 03:57

Message:
Logged In: YES 
user_id=75003

Ok, it seems I misunderstood your sentences regarding
autoconf. It souded to me as if you had run autoconf before
using the configure. The toplevel configure not working the
toplevel directory is a bug IMO, we should fix that. Take 4
is how AS is building memchan for ActiveTcl. I actually
never build from within the source tree anymore, no
extension. Guess that is why this slipped through.

Well, this is to short before my vacation, so I will do
nothing on this before the new year. Note however that Pat
has CVS write access, and has already fixed bugs, albeit in
the code, not the build system.

----------------------------------------------------------------------

Comment By: Joe English (jenglish)
Date: 2004-12-07 03:37

Message:
Logged In: YES 
user_id=68433

> Why are you running autoconf ?

I didn't run autoconf; just 'configure' and 'make' in
various directories (see above).

> Is the configure in the distribution not suitable ?

The one in unix/ does not seem to work at all.  The one in
the top-level directory doesn't work if you run it in the
top-level directory (which is what README.install says to do.)

----------------------------------------------------------------------

Comment By: Andreas Kupries (andreas_kupries)
Date: 2004-12-07 00:22

Message:
Logged In: YES 
user_id=75003

Note: AS uses the toplevel configure to build. No problems.
Might be useful to attach the outputs of the various
commands to this report.

----------------------------------------------------------------------

Comment By: Andreas Kupries (andreas_kupries)
Date: 2004-12-07 00:21

Message:
Logged In: YES 
user_id=75003

Why are you running autoconf ?
Is the configure in the distribution not suitable ?
Which autoconf ? 2.13, 2.5x ?
IIRC this is old TEA, based on autoconf 2.13.

The configure under unix is even older. This is actually
something I wish to drop. Yes, it is not maintained.

----------------------------------------------------------------------

Comment By: Joe English (jenglish)
Date: 2004-12-07 00:14

Message:
Logged In: YES 
user_id=68433

Further analysis: 

Cause of failure in case (1): autoconf is trying to be
"helpful" by mangling the VPATH line.  (AFAICT, this is to
avoid a bug in an old version of 'make' found on an obsolete
version of SunOS; it has the unfortunate side effect of
screwing things up on modern systems.)  

The autoconf manual recommends:

VPATH = @srcdir@

but that probably won't work for memchan since it has source
files spread out across multiple subdirectories.

Case (2): It looks like the configure.in, Makefile.in, and
other build infrastructure files in this directory are
obsolete and no longer maintained.  Didn't investigate
further; perhaps they should be removed from the distribution?

Case (3): Didn't investigate further; probably caused by
../configure picking up the wrong Makefile.in (the one in .
instead of ..)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410295&aid=1080325&group_id=34191