Geert Stappers wrote:> Op 2013-08-05 om 16:11 schreef Dash Four: > >> Geert Stappers wrote: >> >>> Op 2013-08-05 om 12:29 schreef Dash Four: >>> >>>> Well, I am preparing the image using livecd-creator to install all >>>> the packages. This never completes, however, because there is a >>>> dependency on the syslinux package, which is never satisfied since I >>>> can't build that package. >>>> >>>> The actual boot loader is unlikely to be used at all, since >>>> RaspberryPi has its own way of booting up (it relies on its GPU): >>>> when powered up, *only* the GPU is active, which reads certain files >>>> on the first partition (config.txt, cmdline.txt to name just a few), >>>> parses the options specified in those boot up files, then it brings >>>> the CPU up, loads the kernel image from the same partition and >>>> transfers control over. >>>> >>>> So, since my only purpose of using syslinux is to satisfy the >>>> dependencies when creating the actual image (I then extract the >>>> kernel/initramfs images and use the root system), I only need >>>> syslinux to "fool" livecd-creator that I have that package >>>> installed, but I am unable to do that at present since I can't build >>>> the actual package (rpm), hence my initial query. >>>> >>> Welcome to the world outside of x86 >>> >> What's that supposed to mean? >> > > As it says 'Welcome to the world outside of x86' > > It is a "Welcome", so a friendly greeting. > And it implies that you are entering a new world. > > Feel comfortable, you are about to learn more about your known (x86 only) world > by discovering a new world, this time the Rpi world. You will see > different bootloaders, cross-compilers, executable formats. >You can take that patronising crap you've written above and shove it back where the sun doesn't shine, sweetheart! I have asked for help on a specific topic (and yes, I know what the world outside x86 looks like, thank you very much) - if you are unwilling/unable to provide it, please move along, there is nothing to see here.> Back to the original topic: > > Reconsider the (hard??) dependency on Syslinux by "livecd-creator". > > > Or even to use something else as a "CD creator" >livecd-creator is the tool I use to build my images as I have been doing for the best part of 10 years. I use it, because it does the dirty work for me and it (usually) works well, so that I don't have to execute various shell scripts and build that image "manually" so to speak. I've managed to thwart the syslinux dependencies by creating a "dummy" package, so I resolved my little conundrum for the time being.
On Mon, Aug 5, 2013 at 5:40 PM, Dash Four <mr.dash.four at googlemail.com> wrote:> livecd-creator is the tool I use to build my images as I have been doing for > the best part of 10 years. I use it, because it does the dirty work for me > and it (usually) works well, so that I don't have to execute various shell > scripts and build that image "manually" so to speak.I'm willing to bet that livecd-creator was created just for Intel x86/x86-64 (aka IA32/IA32-64, x64) and use it for an ARM (Raspberry Pi), a use that was never coded for nor anticipated. - You are using livecd-creator to build your environment, an open source solution to build a live CD with numerous python scripts. - livecd-creator has a hard-coded requirement of Syslinux (unless the Syslinux-specific build and ISO generation components are removed/disabled) - Syslinux is only intended for (and likely buildable on) x86/x86-64 - Your build target is a Raspberry Pi, an architecture that isn't compatible with Intel x86/x86-64.> I've managed to thwart the syslinux dependencies by creating a "dummy" > package, so I resolved my little conundrum for the time being.Well, that removes one of the constraints. -- -Gene
Gene Cumm wrote:> On Mon, Aug 5, 2013 at 5:40 PM, Dash Four <mr.dash.four at googlemail.com> wrote: > >> livecd-creator is the tool I use to build my images as I have been doing for >> the best part of 10 years. I use it, because it does the dirty work for me >> and it (usually) works well, so that I don't have to execute various shell >> scripts and build that image "manually" so to speak. >> > > I'm willing to bet that livecd-creator was created just for Intel > x86/x86-64 (aka IA32/IA32-64, x64) and use it for an ARM (Raspberry > Pi), a use that was never coded for nor anticipated. >Nope. I am using it to build images for other arches (ppc being one) without problems.> - You are using livecd-creator to build your environment, an open > source solution to build a live CD with numerous python scripts. >Correct.> - livecd-creator has a hard-coded requirement of Syslinux (unless the > Syslinux-specific build and ISO generation components are > removed/disabled) >Nope. As I already pointed out above, I am using it to build images for E604 (ppc-based CPU) and that system doesn't have syslinux installed (it relies on a modified version of u-boot).> - Syslinux is only intended for (and likely buildable on) x86/x86-64 > - Your build target is a Raspberry Pi, an architecture that isn't > compatible with Intel x86/x86-64. >Nope - see above.>> I've managed to thwart the syslinux dependencies by creating a "dummy" >> package, so I resolved my little conundrum for the time being. >> > > Well, that removes one of the constraints. >Indeed it does.