While I can't help with the compilation, here's a quick tip to catch all the output:
make > errors.log 2>&1
That'll ensure all output (stdout and stderr) gets piped to errors.log.
Of course you can use any file and any command.
HTH,
--
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+u...@googlegroups.com.
To post to this group, send email to MOO-...@googlegroups.com.
Visit this group at https://groups.google.com/group/MOO-talk.
For more options, visit https://groups.google.com/d/optout.
While I can't help with the compilation, here's a quick tip to catch all the output:
make > errors.log 2>&1
That'll ensure all output (stdout and stderr) gets piped to errors.log.
Of course you can use any file and any command.
HTH,
On 11/09/2017 18:08, Nathan Smith wrote:
hello folks who know more than me. :)--
As you may know I have been delving into patching recently, and thanks to tidbits of advice, and what not, am getting my head around how .orig and .redge files work. They're really quite interesting.
At any rate, I had one or two questions.
ext-gdbm by martian and moosql. I'd like to get one of them working on my server, I honestly don't care which.
As it happens... Neither do :(
I'm wondering, are martians extentions still valid? none, and I mean none, of the ones I've tried from lisdude.com have worked. Even nprogs breaks! Luckily, some of martians are in gamma already, such as isa(), which is nice, but I'd really like nprogs! My ssh client scrolls too quick for me to get a full error, but it seems to be saying something about undefined reference to mysql_close()? that's for the mysql one, the ext-gdbm just... first, it wasn't finding stdlib.h, so I included it with the my-stdlib.h, and it still errored out.
I'd appreciate any advice in this matter.
Also I am curious if anyone has advise about server convertion, gamma to lambda, gamma to stunt? I have a feeling it can *not* be done, but I know of a person who went from gamma to stunt, though a different version of gamma. Hmm, perhaps a topic for another thread.
Anyway, any help is appreciated.
Thanks for reading, and in particular, thanks to those people who develop patches... they look awesome! lol
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+unsubscribe@googlegroups.com.
To post to this group, send email to MOO-...@googlegroups.com.
Visit this group at https://groups.google.com/group/MOO-talk.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+unsubscribe@googlegroups.com.
A word of caution on the MOO SQL patches floating around. As far as I know, they all block while the the query is running. For example SELECT SLEEP(10) will make your MOO server not process any commands until the query is complete. While you'd probably never run that specific query in practice, if you are doing some expensive querying, it can become noticeable. It's also only compatible with MySQL (and not Postgres), which is rather unfortunate.As far as fixing your error, I think you might need to install some development package for MySQL? Probably named mysql-devel or something like that -- I don't know your Linux distro.
On Mon, Sep 11, 2017 at 5:30 PM, 'Chris Norman' via MOO Talk <MOO-...@googlegroups.com> wrote:
While I can't help with the compilation, here's a quick tip to catch all the output:
make > errors.log 2>&1
That'll ensure all output (stdout and stderr) gets piped to errors.log.
Of course you can use any file and any command.
HTH,
On 11/09/2017 18:08, Nathan Smith wrote:
hello folks who know more than me. :)--
As you may know I have been delving into patching recently, and thanks to tidbits of advice, and what not, am getting my head around how .orig and .redge files work. They're really quite interesting.
At any rate, I had one or two questions.
ext-gdbm by martian and moosql. I'd like to get one of them working on my server, I honestly don't care which.
As it happens... Neither do :(
I'm wondering, are martians extentions still valid? none, and I mean none, of the ones I've tried from lisdude.com have worked. Even nprogs breaks! Luckily, some of martians are in gamma already, such as isa(), which is nice, but I'd really like nprogs! My ssh client scrolls too quick for me to get a full error, but it seems to be saying something about undefined reference to mysql_close()? that's for the mysql one, the ext-gdbm just... first, it wasn't finding stdlib.h, so I included it with the my-stdlib.h, and it still errored out.
I'd appreciate any advice in this matter.
Also I am curious if anyone has advise about server convertion, gamma to lambda, gamma to stunt? I have a feeling it can *not* be done, but I know of a person who went from gamma to stunt, though a different version of gamma. Hmm, perhaps a topic for another thread.
Anyway, any help is appreciated.
Thanks for reading, and in particular, thanks to those people who develop patches... they look awesome! lol
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+u...@googlegroups.com.
To post to this group, send email to MOO-...@googlegroups.com.
Visit this group at https://groups.google.com/group/MOO-talk.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+u...@googlegroups.com.