WebGUI looked good, but I couldn’t seem to get it working correctly. I tried a couple of other things, but none of those panned out, either. So I’ve decided to convert my main site back to Moin.
I used Moin on my main site back in the early 1.5-ish days and it worked rather well. I can’t remember why I changed, though it could well have been one of the many service provider moves I made. At any rate, Moin gives me the flexibility that I want, and I’m not terribly scared of Python if I want to get into some of the code that runs it.
I’ll eventually get my blog moved back there. While WordPress does blogs well I would rather keep everything together on one site. For some reason it gives me warm fuzzies.
On a whim I decided to have a peek about for a content management system that suits my needs. After a little poking about Freshmeat I came across WebGUI, which looks pretty interesting.
A couple of the obvious features I like are that it’s written in Perl and has a good security policy. Of course, TWiki is written in Perl and has a security alerts page, so that doesn’t guarantee much. WebGUI is shipped ready-to-go in binary form, and is ostensibly pre-configured, which I figure should save me from making too many foolish mistakes. Time will tell.
I’m going to give it a go on my main site soon. Photos don’t put themselves on-line!
Got a few good search terms to respond to again, so here goes:
twiki install centos 5.1: Don’t do it unless you know what you’re getting into. I had a bad security experience likely caused by Twiki, and I’ve seen a lot of people reporting similar experiences that they are convinced was Twiki’s fault. At the very least, google “twiki security” before you do it. The codebase is much too large for a single person to audit it in a reasonable amount of time. If you need a good Wiki in general, give Moin a try. Consider using a Wiki hosting service, where someone else has to worry about the security of the underlying machine. Or just don’t use a Wiki at all — unless you truly want what a Wiki in specific has to offer.
iphone unofficial toolchain easiest way: There is no easy way. There is drudge’s way that I point to in another entry, but aside from that I didn’t find any way that was at all easy. binutils can be convinced to generate (possibly-working) tools for arm-apple-darwin fairly easily, but I think GCC is a bit trickier. Don’t try to do it on your own unless you want to spend a lot of time making the tools work rather than using them.
do peanuts have gluten?: Nope, peanuts don’t have gluten in them. They may have gluten on them, though — it depends on how they’ve been processed or flavoured. When in doubt, read the label and assume that “spices” includes something gluten-based. I’ve seen some with and some without gluten, so have a look around.
According to the iPhone SDK ReadMe, the beta version of the SDK isn’t exactly ready to go on 64-bit systems. Given that I’m using a 64-bit system this may explain Error 34 and some of the other strangeness I encountered.
I’m also running into walls left, right, and centre in my plan to get GCC running on the iPod Touch. I had also forgotten about Perl‘s perverse configuration process, which doesn’t lend itself easily to cross-compiling.
At this point I think I’m going to punt on building Perl for the iPod until the official SDK is released and I can get on the developer program. The fact that this will almost certainly take several months (until Apple is ready to accept non-Americans) is annoying to me, but there’s naught that can be done about it — I simply don’t have the knowledge to port GCC to the iPod, and that seems to be the most sane way to get these things going.
I’m trying to build bison for arm-apple-darwin and I’m running into a bit of trouble that looks like it originates in autoconf and/or friends. As configure runs, it checks for strndup to be declared and for it to be usable, and it claims it’s not declared but it is usable. The build fails with an unresolved symbol _strndup. The even odder part is that there is an implementation of strndup in the lib library, and it seems to get linked into libbison.a, but nm shows the symbol as being unresolved. This is probably due to some preprocessor magic going on in the implementation file.
Is there anyone out there who knows a bit about autoconf or how bison (or similar projects) fit together who can give me some clue as to what’s going on? I’m a total autotools newbie.
I’ll see what other deps I can pull together in the meantime.
I’ve started to build a few packages that will help me build Perl building on the iPod Touch. Rather than try to cross-compile Perl, I’ve decided to cross-compile what I need to get a development environment going on the iPod itself. It means much longer builds but much quicker total development time — or at least that’s what I’m hoping for.
So far I’ve got flex 2.5.35, libiconv 1.12, libtool 2.2, and m4 1.4.10. They’ve all been pretty easy, with the only hiccup coming when the flex build #defined malloc to rpl_malloc, apparently because the autoconf macros AC_FUNC_MALLOC and AC_FUNC_REALLOC set that up if they detect functions that aren’t GNU-compatible. Unfortunately, there’s no implementation of rpl_malloc or rpl_realloc available, so the build died when the symbols couldn’t be found in the libraries.
For the moment I’m just keeping shell scripts that patch files (where necessary) and run configure with the appropriate arguments. I’ll throw them up on my website tomorrow when I get a chance. I’ll update this entry with the link. If anyone has any advice moving forward I’d love to hear it — especially if I’m going about things the wrong way. I just have no clue when it comes to autoconf and friends.
Update: The first packages are up at https://www.kjwcode.com/project/idev/. More will be on the way.
After realising that the iPhone/iPod Touch SDK isn’t going to do what I want it to do yet, I am experimenting with various ways of doing what I actually want to do — run programs on my iPod Touch, not a simulator.
My first try is drudge’s HOWTO build the toolchain on Leopard, and it looks good so far, which is to say that I’ve got “hello world” running on my iPod. It seems to include everything you’d need.
The next big question is how to package things up for installation onto the device. For now I’m going to assume that people can scp things to their device and ssh into it (or use a terminal) to do the installation. I will likely get the Installer packages built eventually, though.