I know you built minimyth using mandrake.. I use gentoo so I'm sure their would be some problems using the binaries I've made, but perhaps I can just install mdk on a VMWare machine and build modules from there, and copy them over to the rootfs? Is it more complicated than that?
[EDIT] Oops.. looks like I posted in the wrong forum.. should be in General Help, I guess. Mod: can you move this?
My current thinking is to allow people to build minimyth from scratch easily (sort of like gentoo). I think GAR (from linux-bbc) will allow me to do this but I have only read some of the documentation. It's a big project and it will take me a while.
Once it is done, someone could add a module w/ GAR stuff so that the rest of us could also build it. I'm not sure but you could probably even configure it to grab latest CVS from Mythtv.org so we wouldn't necessarily have to align with major mythtv releases.
Let me know what you think, I need a project to keep my unemployed ass busy and out of the bars.
At the moment, I am working on an article describing how I built minimyth-0.1. Perhaps I can send you what I have, which would hopefully be enough to tell you what I need GAR to do.
The article is not complete yet (in particular, I have not verified the steps yet , but you could shoot me an email if you run into any problems.
I was thinking about possible problems/issues and came up with a couple. I think that glibc needs to match between the host system and MiniMyth so someone running something like Debian stable would run into trouble. Actually all the problems would be from which development system was used but it would be easy enough to make a chroot environment.
Hope to hear from you soon,
Yup, been working on it, have the base system done but X doesn't want to cooperate. It bombs out on the via driver (undefined reference to `MPGDevice') which I suspect is in libddmpeg.a but Ivor's site is down so can't tell for sure right now. My big plan is to finish it up and test it out tomorrow on my epia. Should have something to show soon.lmatter wrote:
DNA, I emailed the locataion of the article to you, let me know if you got it.
I'm not really sure about what to do with glibc. I'm building on a Gentoo box all optimized for i686 so I have to rebuild it to run on an epia but I'm not sure if this is something anyone else would want to do. Its also super easy to set it up to compile against uClibc (assuming all the progs play nice) and save a meg or two.
WRT to X bombing, which version are you using and are you using my host.def file? And I think for now we'll just copy the Via binary drivers from linpvr until a real open-source solution is found.
I've copied the via drivers to http://linpvr.org/viadrv/
WRT glibc that does sound like a problem. For the short term I would say if you want to build for an Ezra CPU, then your build machine's glibc should be i586, and not i686 optimized. We can talk about how to solve it for the longer term, but I woudn't want this to hold us up.
And as far as uClibc is concerned, I had some bad experiences with it (like one might have a bad experience with Tequila) and so I would like to avoid it for now.
Thanks for your work!
BTW, I continue to update the articles so you might want to check back once in a while.
I've been using 126.96.36.199. I think the link to your host.def was down when I started playing with X so I modified the freevix one. I have it only building the via driver but I also messed with some other settings so maybe I broke something. It built fine with the stock freevix host.def before I started changing things, I'll figure out what's up. You are using the Alan Cox via driver in the XFree source, right? I think I'll save this for last since it takes so damn long to compile.WRT to X bombing, which version are you using and are you using my host.def file? And I think for now we'll just copy the Via binary drivers from linpvr until a real open-source solution is found.
Not really a problem, its just that I'm building everything on my laptop cause its lots faster than a ME6000. I have to rebuild glibc anyway I was just wondering if you wanted it as part of the build process or set up to copy the host binaries. Its a pretty trivial change, it just has to be one or the other.WRT glibc that does sound like a problem. For the short term I would say if you want to build for an Ezra CPU, then your build machine's glibc should be i586, and not i686 optimized. We can talk about how to solve it for the longer term, but I woudn't want this to hold us up.
Well, off to Taco Hell and then see if I can't get this thing finished today.
Mine will only enable mmx, not sse or 3dnow, so that it works on both ezra and nehemiah. I was using Alan's driver for minimyth-0.1, but for 0.2 I am using a binary driver supplied by Via built against the kernel I am using.
wrt glibc, my tendancy is to not build it because I am naturally lazy and impatient. But if there is a way to include it but comment it out for others that might need it that would be good. And on second thought, I'll probably kick this thing off at night anyways, so if it has to build glibc then that is probably ok.
Mmm, taco bell. I like the new fiesta chicken bowl.
ssl <-- for X?
mysqlclient <-- is this from a standard mysql install?
X builds now, I guess I changed the wrong setting but I added your host.def to be safe. If I could get a look at your install script I'll add it in too.
Should be ready for testing very soon
Umm, don't have one. Scripting is not my strong suit. When I execute the mkcramfs command, I just specify the output as /var/lib/tftpboot/PXEClient (and therefore I run it as root).If I could get a look at your install script I'll add it in too.
Still "almost done". Took care of all the libs, now I just have linc, mythTV, mysql and a little tweaking left. I hopefully can test it out tonight, I'm planning to have my epia as a frontend/backend so I can't really test the mythTV part but I'll make sure it boots and X works.
I'll keep you updated.