Closed GoogleCodeExporter closed 8 years ago
Let me know how this works for you with the new --linkify option in SVN. By
default,
only fully qualified URLs are recognized. But a more aggressive mode is
available
where ShellInABox will also recognize URLs, hostnames, and e-mail addresses
that are
not preceded by a protocol.
Only http://, https://, ftp://, and mailto: are recognized protocols. Let me
know, if
you think others need to be included in the list.
Original comment by zod...@gmail.com
on 4 Jul 2009 at 8:18
Attempting to try this from SVN, I'm getting an error:
$ make
cd . && /bin/sh /home/tony/shellinabox-read-only/missing --run autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
make all-am
make[1]: Entering directory `/home/tony/shellinabox-read-only'
/bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -g
-std=gnu99
-Wall -Os -MT hashmap.lo -MD -MP -MF .deps/hashmap.Tpo -c -o hashmap.lo `test -f
'libhttp/hashmap.c' || echo './'`libhttp/hashmap.c
./libtool: line 467: CDPATH: command not found
./libtool: line 1145: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6 Debian-2.2.6a-4, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
Debian-2.2.6a-4
libtool: and run autoconf again.
make[1]: *** [hashmap.lo] Error 63
make[1]: Leaving directory `/home/tony/shellinabox-read-only'
make: *** [all] Error 2
Original comment by gnute...@gmail.com
on 4 Jul 2009 at 12:47
I am very puzzled how that would happen. You should have all the files you need
in
SVN, and it should be able to configure your source tree from those files.
I just tried on a bunch of different test machines that I have access to, and
they
all build just fine from SVN.
Maybe, SVN didn't correctly reproduce time stamps and is trying to build files
that
it shouldn't rebuild?
In any case, the thing that should always work is for you to install all the GNU
autotools (including automake, autoconfig, and libtool). You can then run the
"autoreconf" command and it will reconfigure the source files to use the
scripts that
are installed on your machine.
Alternatively, download the attached tar archive and build from those sources.
That
should always work. If it doesn't, something is seriously misconfigured
somewhere.
Original comment by zod...@gmail.com
on 4 Jul 2009 at 5:23
Attachments:
A pristine pull from SVN worked. My apologies, I should have tried that before
wasting your time.
Build works, and initial testing of the linkify stuff looks like it works fine.
My
life is complete :-)
Thanks
Original comment by gnute...@gmail.com
on 5 Jul 2009 at 1:56
Original issue reported on code.google.com by
gnute...@gmail.com
on 21 Jun 2009 at 11:43