Hey all

I found a bug in the SSH server in magicka that if triggered would cause
100% cpu usage, as it would enter a never ending loop.

It's fixed in v0.10-patch and v0.11-alpha

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Just trying to set up fresh... but bit stuck as to the best way to do it to install something that is 'the latest' ... do you think there's any way I can update from the version I currently have set up or is it better to start over fresh?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Just trying to set up fresh... but bit stuck as to the best way to do
it to install something that is 'the latest' ... do you think there's
any way I can update from the version I currently have set up or is
it better to start over fresh?

I'd say seeing it's 0.7-alpha starting fresh would probably be the way to
go. You should be able to salvage most of your settings, but I'd redo the bbs.ini (or at least check for new lines).

Your magimail prefs should be fine.

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 05/31/18, Avon said the following...

Just trying to set up fresh... but bit stuck as to the best way to do it to install something that is 'the latest' ... do you think there's any
way I can update from the version I currently have set up or is it
better to start over fresh?

I did a fresh install and just moved the config files, userlist, and my ANSI screens...

Regards

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: New Frontier 2| thenewfrontier2.hopto.org (Ohio) (21:2/105)

On 05/31/18, KrUpTiOn pondered and said...

I did a fresh install and just moved the config files, userlist, and my ANSI screens...

I thought I'd pulled down the latest version but when I ran the first script all went well but I could not seem to start the BBS up.
I'm also unsure about the correct Git commands to use so I can install the latest versions.. I'll play some more tonight when I get home :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'd say seeing it's 0.7-alpha starting fresh would probably be the way to go. You should be able to salvage most of your settings, but I'd redo the bbs.ini (or at least check for new lines).

Your magimail prefs should be fine.

Thanks :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 05/31/18, KrUpTiOn pondered and said...

I thought I'd pulled down the latest version but when I ran the first script all went well but I could not seem to start the BBS up. I'm also unsure about the correct Git commands to use so I can install the latest versions.. I'll play some more tonight when I get home :)

It's the same way you pulled that version, just have to change it from
.07 to .10-alpha (I think that's it) do it from the magickabbs folder.
I might pull .11, I think apam said that's available too (with a few
possible bugs), which I wouldn't mind running just to see if I can help
him out find anything wrong with it. I do like Magicka! I still gotta
figure why my doors won't run.

Regards


--- MagickaBBS v0.10patch (Linux/x86_64)
* Origin: The New Frontier][ - thenewfrontier2.hopto.org (Ohio) (21:2/105.3)

On 06/02/18, KrUpTiOn pondered and said...

It's the same way you pulled that version, just have to change it from
.07 to .10-alpha (I think that's it) do it from the magickabbs folder.
I might pull .11, I think apam said that's available too (with a few

Yep I need to start over I think...

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 05/14/18, apam pondered and said...

Hey

Hey

If you want to update:

git pull

git checkout v0.10-patch

or if you want the latest

git pull

git checkout v0.11-alpha

I'm trying to follow the install docs on your site and opted to checkout the latest alpha then ran make www

[snip]

In file included from www.c:15:0:
bbs.h:386:14: note: expected 'char *' but argument is of type 'const char *'
extern char *www_decode_hash(char *hash);
^
Makefile.linux.WWW:47: recipe for target 'www.o' failed
make[1]: *** [www.o] Error 1
make[1]: Leaving directory '/home/pi/MagickaBBS/src'
Makefile:33: recipe for target 'www' failed
make: *** [www] Error 2


[snip]

Can you tell me if I am doing something wrong?

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

No I don't think so, what are you compiling on? like what linux
distribution?

gcc has been getting more picky about warnings, so I might have to do
something to fix it.

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/10/18, apam pondered and said...

No I don't think so, what are you compiling on? like what linux distribution?

gcc has been getting more picky about warnings, so I might have to do something to fix it.

Raspberry Pi... I also used the commands at the start of the docs to update
and install the listed dependencies/modules? before I started.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/10/18, apam pondered and said...

No I don't think so, what are you compiling on? like what linux distribution?

gcc has been getting more picky about warnings, so I might have t something to fix it.

Raspberry Pi... I also used the commands at the start of the docs to
update and install the listed dependencies/modules? before I started.

Hmm, can you copy a bit more of the output than you posted last time, I
think you might have snipped the important part. Do you know if you're on raspbian stretch or jessie?

Also, does it compile without the www, ie just make instead of make www

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/10/18, apam pondered and said...

Hmm, can you copy a bit more of the output than you posted last time, I

[snip]

pi@raspberrypi:~/MagickaBBS $ make www
cd src && make -f Makefile.linux.WWW
make[1]: Entering directory '/home/pi/MagickaBBS/src'
cc -c -o www.o www.c -std=gnu99 -I/usr/local/include -I../deps/ -I../deps/libb64-1.2/include -DENABLE_WWW=1
www.c: In function 'www_auth_ok':
www.c:357:14: warning: initialization discards 'const' qualifier from pointer target type
char *ptr = MHD_lookup_connection_value(connection, MHD_HEADER_KIND, "Authorization");
^
www.c: In function 'www_handler':
www.c:992:44: error: 'MHD_HTTP_HEADER_CONTENT_DISPOSITION' undeclared (first use in this function)
MHD_add_response_header(response, MHD_HTTP_HEADER_CONTENT_DISPOSITION, buffer);
^
www.c:992:44: note: each undeclared identifier is reported only once for each function it appears in
www.c:1032:31: warning: passing argument 1 of 'www_decode_hash' discards 'const' qualifier from pointer target type
filename = www_decode_hash(&url[7]);
^
In file included from www.c:15:0:
bbs.h:386:14: note: expected 'char *' but argument is of type 'const char *'
extern char *www_decode_hash(char *hash);
^
Makefile.linux.WWW:47: recipe for target 'www.o' failed
make[1]: *** [www.o] Error 1
make[1]: Leaving directory '/home/pi/MagickaBBS/src'
Makefile:33: recipe for target 'www' failed
make: *** [www] Error 2

[snip]

..that's all I got.. :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/10/18, apam pondered and said...

Also, does it compile without the www, ie just make instead of make www

Nope...

Warning lot's of output to follow.

[snip]

pi@raspberrypi:~/MagickaBBS $ make
cd src && make -f Makefile.linux
make[1]: Entering directory '/home/pi/MagickaBBS/src'
cc -c -o bluewave.o bluewave.c -std=gnu99 -I/usr/local/include -I../deps/
cc -c -o hashmap/hashmap.o hashmap/hashmap.c -std=gnu99 -I/usr/local/include -I../deps/
cc -c -o menus.o menus.c -std=gnu99 -I/usr/local/include -I../deps/
cc -c -o nodelist.o nodelist.c -std=gnu99 -I/usr/local/include -I../deps/
cc -c -o blog.o blog.c -std=gnu99 -I/usr/local/include -I../deps/
cd ../deps/lua && make -f Makefile linux MAKEFLAGS=
make[2]: Entering directory '/home/pi/MagickaBBS/deps/lua'
make all SYSCFLAGS="-DLUA_USE_LINUX" SYSLIBS="-Wl,-E -ldl -lreadline"
make[3]: Entering directory '/home/pi/MagickaBBS/deps/lua'
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lapi.o lapi.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lcode.o lcode.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lctype.o lctype.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ldebug.o ldebug.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ldo.o ldo.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ldump.o ldump.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lfunc.o lfunc.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lgc.o lgc.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o llex.o llex.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lmem.o lmem.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lobject.o lobject.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lopcodes.o lopcodes.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lparser.o lparser.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lstate.o lstate.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lstring.o lstring.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ltable.o ltable.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ltm.o ltm.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lundump.o lundump.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lvm.o lvm.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lzio.o lzio.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lauxlib.o lauxlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lbaselib.o lbaselib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lbitlib.o lbitlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lcorolib.o lcorolib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ldblib.o ldblib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o liolib.o liolib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lmathlib.o lmathlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o loslib.o loslib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lstrlib.o lstrlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o ltablib.o ltablib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o lutf8lib.o lutf8lib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o loadlib.o loadlib.c
gcc -std=gnu99 -O2 -Wall -Wextra -DLUA_COMPAT_5_2 -DLUA_USE_LINUX -c -o linit.o linit.c
ar rcu liblua.a lapi.o lcode.o lctype.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o
ltm.o lundump.o lvm.o lzio.o lauxlib.o lbaselib.o lbitlib.o lcorolib.o
ldblib.o liolib.o lmathlib.o loslib.o lstrlib.o ltablib.o lutf8lib.o
loadlib.o linit.o
ranlib liblua.a
make[3]: Leaving directory '/home/pi/MagickaBBS/deps/lua'
make[2]: Leaving directory '/home/pi/MagickaBBS/deps/lua'
cd ../deps/Xmodem && make MAKEFLAGS=
make[2]: Entering directory '/home/pi/MagickaBBS/deps/Xmodem'
cc -O -I.. -DHAVE_STRDUP -c -o crctab.o crctab.c
cc -O -I.. -DHAVE_STRDUP -c -o seriallog.o seriallog.c
cc -O -I.. -DHAVE_STRDUP -c -o zmodem.o zmodem.c
cc -O -I.. -DHAVE_STRDUP -c -o zmodemr.o zmodemr.c
cc -O -I.. -DHAVE_STRDUP -c -o zmodemsys.o zmodemsys.c
cc -O -I.. -DHAVE_STRDUP -c -o zmodemt.o zmodemt.c
cc -O -I.. -DHAVE_STRDUP -c -o zmutil.o zmutil.c
rm -f libzmodem.a
ar cru libzmodem.a crctab.o seriallog.o zmodem.o zmodemr.o zmodemsys.o zmodemt.o zmutil.o
ranlib libzmodem.a
make[2]: Leaving directory '/home/pi/MagickaBBS/deps/Xmodem'
cd ../deps/jamlib && make -f Makefile.linux MAKEFLAGS=
make[2]: Entering directory '/home/pi/MagickaBBS/deps/jamlib'
cc -D__LINUX__ -Wall -c crc32.c -o crc32.o
cc -D__LINUX__ -Wall -c mbase.c -o mbase.o
cc -D__LINUX__ -Wall -c message.c -o message.o
message.c: In function 'JAM_ReadMsgHeader':
message.c:145:28: warning: pointer targets in passing argument 1 of 'getjamsubfield' differ in signedness [-Wpointer-sign]
getjamsubfield(Ptr_PC,&Subfield_S);
^
In file included from message.c:61:0:
structrw.h:84:6: note: expected 'unsigned char *' but argument is of type
'char *'
void getjamsubfield(unsigned char *buf,s_JamSubfield *Subfield_S);
^
cc -D__LINUX__ -Wall -c lastread.c -o lastread.o
cc -D__LINUX__ -Wall -c subpack.c -o subpack.o
cc -D__LINUX__ -Wall -c structrw.c -o structrw.o
ar -ru jamlib.a crc32.o mbase.o message.o lastread.o subpack.o structrw.o
ar: creating jamlib.a
make[2]: Leaving directory '/home/pi/MagickaBBS/deps/jamlib'
cd ../deps/jsmn/ && make
make[2]: Entering directory '/home/pi/MagickaBBS/deps/jsmn'
cc -c jsmn.c -o jsmn.o
ar rc libjsmn.a jsmn.o
make[2]: Leaving directory '/home/pi/MagickaBBS/deps/jsmn'
rm ../deps/libuuid/ltmain.sh ../deps/libuuid/libtool || true
rm: cannot remove '../deps/libuuid/libtool': No such file or directory
cd ../deps/libuuid/ && libtoolize
libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
cd ../deps/libuuid/ && autoreconf
/bin/sh: 1: autoreconf: not found
Makefile.linux:34: recipe for target '../deps/libuuid/.libs/libuuid.a' failed make[1]: *** [../deps/libuuid/.libs/libuuid.a] Error 127
make[1]: Leaving directory '/home/pi/MagickaBBS/src'
Makefile:30: recipe for target 'magicka' failed
make: *** [magicka] Error 2

[snip]

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

www.c: In function 'www_handler':
www.c:992:44: error: 'MHD_HTTP_HEADER_CONTENT_DISPOSITION' undeclared (first use in this function)
MHD_add_response_header(response, MHD_HTTP_HEADER_CONTENT_DISPOSITION, buffer);

This bit is the error, it means the libmicrohttpd you have is too old,
which probably means you're running raspbian jessie, you can either
upgrade to raspbian stretch, download libmicrohttpd from the GNU ftp
server and compile a more recent version manually, or just compile
magicka without HTTP support.

If you just want to play with the BBS side of things and don't care about
the web interface, the last solution will probably be the easiest.

To do this run:

make cleanwww
make

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/10/18, apam pondered and said...

Also, does it compile without the www, ie just make instead of ma

Nope...

Ah, looks like you're missing autotools, try sudo apt-get install
automake then try again.

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/11/18, apam pondered and said...

This bit is the error, it means the libmicrohttpd you have is too old, which probably means you're running raspbian jessie, you can either upgrade to raspbian stretch, download libmicrohttpd from the GNU ftp

Cool thanks, I am trying to update to stretch as I type.. it may take a while as the Pi is slooowww...

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/11/18, apam pondered and said...

Ah, looks like you're missing autotools, try sudo apt-get install
automake then try again.

Looks like the OS update is going to take an hour or so, so I will leave it
to run overnight and try again to progress tomorrow.. it's not for want of trying :)

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/11/18, apam pondered and said...

Ah, looks like you're missing autotools, try sudo apt-get install automake then try again.

Looks like the OS update is going to take an hour or so, so I will
leave it to run overnight and try again to progress tomorrow.. it's
not for want of trying :)

Hehe all good, you'll still need automake and things it's a new
dependency in v0.11 to build libuuid (which is part of the mnet stuff)..

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/11/18, apam pondered and said...

Looks like the OS update is going to take an hour or so, so I will leave it to run overnight and try again to progress tomorrow.. it's not for want of trying :)

Hehe all good, you'll still need automake and things it's a new
dependency in v0.11 to build libuuid (which is part of the mnet stuff)..

Day 3... I got to the Pi and it reported the download had taken 8 hours... 8 hours! so now I have set it installing and there's lots of slow text
creping up the terminal window...

More to report on Day 4 I think... I heading to zzz soon...

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/12/18, Avon pondered and said...

More to report on Day 4 I think... I heading to zzz soon...

Day 4.. it's like the 12 days of Xmas this :)

I restarted the Pi after it had updated to the new OS and finally got my VNC running again.

Then ran a git pull and tried again

[snip]

pi@raspberrypi:~/MagickaBBS $ git pull
remote: Counting objects: 4, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 0 (delta 0)
Unpacking objects: 100% (4/4), done.
From git://git.magickabbs.com/MagickaBBS
07b5568..760fef4 v0.11-alpha -> origin/v0.11-alpha
Updating 07b5568..760fef4
Fast-forward
src/menus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pi@raspberrypi:~/MagickaBBS $ make
cd src && make -f Makefile.linux
make[1]: Entering directory '/home/pi/MagickaBBS/src'
cc -o ../magicka inih/ini.o bbs.o main.o users.o main_menu.o mail_menu.o doors.o bbs_list.o chat_system.o email.o files.o settings.o lua_glue.o strings.o bluewave.o hashmap/hashmap.o menus.o nodelist.o blog.o ../deps/lua/liblua.a ../deps/Xmodem/libzmodem.a ../deps/jamlib/jamlib.a ../deps/jsmn/libjsmn.a ../deps/libuuid/.libs/libuuid.a -std=gnu99 -I/usr/local/include -I../deps/ -L/usr/local/lib -lsqlite3 -lutil -lm -ldl -lssl -lcrypto -lssh
bbs.o: In function `runbbs_real':
bbs.c:(.text+0x31a4): undefined reference to `www_expire_old_links'
main.o: In function `sigterm_handler':
main.c:(.text+0x70): undefined reference to `MHD_stop_daemon'
main.o: In function `server':
main.c:(.text+0x4220): undefined reference to `www_init'
main.c:(.text+0x4294): undefined reference to `MHD_start_daemon' main.c:(.text+0x430c): undefined reference to `MHD_start_daemon' main.c:(.text+0x4708): undefined reference to `www_handler' main.c:(.text+0x470c): undefined reference to `www_request_completed' main.c:(.text+0x4710): undefined reference to `www_logger'
files.o: In function `genurls':
files.c:(.text+0x2c88): undefined reference to `www_create_link'
collect2: error: ld returned 1 exit status
Makefile.linux:45: recipe for target 'magicka' failed
make[1]: *** [magicka] Error 1
make[1]: Leaving directory '/home/pi/MagickaBBS/src'
Makefile:30: recipe for target 'magicka' failed
make: *** [magicka] Error 2


So that's where I am at the mo ..

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

So that's where I am at the mo ..

Yeah, I'd say you had old files in your source tree from when you did
make www

try:

make cleanwww
make

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/13/18, apam pondered and said...

Yeah, I'd say you had old files in your source tree from when you did
make www

try:

make cleanwww
make

If I run this am I compiling things without the www functionality?

The make cleanwww seems to work

If I run make www after that I still hit errors

[snio]

^
www.c: In function 'www_handler':
www.c:992:44: error: 'MHD_HTTP_HEADER_CONTENT_DISPOSITION' undeclared (first use in this function)
MHD_add_response_header(response, MHD_HTTP_HEADER_CONTENT_DISPOSITION, buffer);
^
www.c:992:44: note: each undeclared identifier is reported only once for each function it appears in
www.c:1032:31: warning: passing argument 1 of 'www_decode_hash' discards 'const' qualifier from pointer target type
filename = www_decode_hash(&url[7]);
^
In file included from www.c:15:0:
bbs.h:386:14: note: expected 'char *' but argument is of type 'const char *'
extern char *www_decode_hash(char *hash);
^
Makefile.linux.WWW:47: recipe for target 'www.o' failed
make[1]: *** [www.o] Error 1
make[1]: Leaving directory '/home/pi/MagickaBBS/src'
Makefile:33: recipe for target 'www' failed
make: *** [www] Error 2

[snip]

automake is installed, I am on the latest os for the pi,

If I run just make then it looks to compile successfully but without the www?

and if I start setting up then try to get the www compiled again do I risk loosing all the configs - right?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

automake is installed, I am on the latest os for the pi,

If I run just make then it looks to compile successfully but without
the www?

and if I start setting up then try to get the www compiled again do I
risk loosing all the configs - right?

No you won't lose any configs.

It looks as though you might still have the old libmicrohttpd package installed. Try running:

apt-get install libmicrohttpd12

And see what happens..

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/16/18, apam pondered and said...

No you won't lose any configs.

Thanks, phew..

It looks as though you might still have the old libmicrohttpd package installed. Try running:
apt-get install libmicrohttpd12

And see what happens..

pi@raspberrypi:~/MagickaBBS $ sudo apt-get install libmicrohttpd12
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libmicrohttpd12

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/16/18, apam pondered and said...

No you won't lose any configs.

Thanks, phew..

It looks as though you might still have the old libmicrohttpd pac installed. Try running:
apt-get install libmicrohttpd12

And see what happens..

pi@raspberrypi:~/MagickaBBS $ sudo apt-get install libmicrohttpd12
Reading package lists... Done Building dependency tree
Reading state information... Done
E: Unable to locate package libmicrohttpd12

Well that is odd. It shows up on my raspberry pi.

What's the output of:

sudo apt-cache search libmicrohttpd

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/16/18, apam pondered and said...

Well that is odd. It shows up on my raspberry pi.

What's the output of:

sudo apt-cache search libmicrohttpd

pi@raspberrypi:~/MagickaBBS $ sudo apt-cache search libmicrohttpd libmicrohttpd-dbg - library embedding HTTP server functionality (debug) libmicrohttpd-dev - library embedding HTTP server functionality (development) libmicrohttpd10 - library embedding HTTP server functionality pi@raspberrypi:~/MagickaBBS $

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'm really not sure what's going on here. Stretch should have
libmicrohttpd12 in it's repo not libmicrohttpd10.

Does your /etc/apt/sources.list have stretch in it or jessie?

Andrew



--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/16/18, apam pondered and said...

I'm really not sure what's going on here. Stretch should have libmicrohttpd12 in it's repo not libmicrohttpd10.

Does your /etc/apt/sources.list have stretch in it or jessie?

I see the following in the sources.list file

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source' #deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free
rpi

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/16/18, apam pondered and said...

I'm really not sure what's going on here. Stretch should have libmicrohttpd12 in it's repo not libmicrohttpd10.

Does your /etc/apt/sources.list have stretch in it or jessie?

I see the following in the sources.list file

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

Hmm. That should say stretch not jessie. I would have thought the upgrade should have changed it. You could try changing it, then do:

sudo apt-get update
sudo apt-get dist-upgrade

Then try and install libmicrohttpd.

However, if you have anything important running on your pi, and really
want to run the web stuff on Magicka, I would consider getting a
different sd card and installing Raspbian Stretch fresh, because it seems somethings gone wrong somewhere with the upgrade.

Andrew

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/16/18, apam pondered and said...

Does your /etc/apt/sources.list have stretch in it or jessie?

I see the following in the sources.list file

deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi

Hmm. That should say stretch not jessie. I would have thought the upgrade should have changed it. You could try changing it, then do:

So would the deb http:// line just change the word jessie to stretch but
leave the rest of the line syntax intact?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 06/16/18, apam pondered and said...

Does your /etc/apt/sources.list have stretch in it or je

I see the following in the sources.list file

deb http://mirrordirector.raspbian.org/raspbian/ jessie main non-free rpi

Hmm. That should say stretch not jessie. I would have thought the should have changed it. You could try changing it, then do:

So would the deb http:// line just change the word jessie to stretch
but leave the rest of the line syntax intact?

Yes

--- MagickaBBS v0.11alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

On 06/16/18, apam pondered and said...

So would the deb http:// line just change the word jessie to stretch but leave the rest of the line syntax intact?

Yes

OK thanks :) I will try this tonight when I get back home... just heading out now.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Hmm. That should say stretch not jessie. I would have thought the u
pgrade
should have changed it. You could try changing it, then do:

I think you have to change it yourself before you do an upgrade from
one version to another. When I upgraded my debian and raspbian
systems, I did a backup then changed the sources.list so that it
pointed to the new version. Then did an apt-get update,
dist-upgrade, etc.

If stretch was not in his sources.list, he would not have gotten any
of the stretch updated programs/code. He would have just got newer
versions of the jessie programs/code.


--- MagickaBBS v0.10patch (Linux/armv7l)
* Origin: Possum Lodge South * capitolcityonline.net:7636 (21:1/175.8)