On 11.07.2015 06:16, Gene Cumm wrote:> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: > >> The same as with the ISOLINUX, stable and git. >> Only this time has nothing to do with the menu. > > 1) EXTLINUX is no longer a discrete variant. The installer extlinux now > installs SYSLINUX. > 2) William Kensington already saw a similar behavior wherein an ISOLINUX > image failed before parsing the config. > 3) It feels like this is a moving target where gcc keeps changing and > different results get reported. > 4) We'll likely need to make code akin to the old tracers (on screen or > serial) to log progress. > > --Gene >Upstream folks could be of help https://bugzilla.redhat.com/show_bug.cgi?id=1243117
On 14.07.2015 21:59, poma wrote:> On 11.07.2015 06:16, Gene Cumm wrote: >> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: >> >>> The same as with the ISOLINUX, stable and git. >>> Only this time has nothing to do with the menu. >> >> 1) EXTLINUX is no longer a discrete variant. The installer extlinux now >> installs SYSLINUX. >> 2) William Kensington already saw a similar behavior wherein an ISOLINUX >> image failed before parsing the config. >> 3) It feels like this is a moving target where gcc keeps changing and >> different results get reported. >> 4) We'll likely need to make code akin to the old tracers (on screen or >> serial) to log progress. >> >> --Gene >> > > > Upstream folks could be of help > https://bugzilla.redhat.com/show_bug.cgi?id=1243117 > >s/Upstream/Downstream/
On 16.07.2015 07:13, poma wrote:> On 14.07.2015 21:59, poma wrote: >> On 11.07.2015 06:16, Gene Cumm wrote: >>> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: >>> >>>> The same as with the ISOLINUX, stable and git. >>>> Only this time has nothing to do with the menu. >>> >>> 1) EXTLINUX is no longer a discrete variant. The installer extlinux now >>> installs SYSLINUX. >>> 2) William Kensington already saw a similar behavior wherein an ISOLINUX >>> image failed before parsing the config. >>> 3) It feels like this is a moving target where gcc keeps changing and >>> different results get reported. >>> 4) We'll likely need to make code akin to the old tracers (on screen or >>> serial) to log progress. >>> >>> --Gene >>> >> >> >> Upstream folks could be of help >> https://bugzilla.redhat.com/show_bug.cgi?id=1243117 >> >> > > s/Upstream/Downstream/ >For the record, current git, built with gcc-4.8.3, both ISOLINUX & EXTLINUX run OK. Test compilation: http://goo.gl/Gm4ffO ISO/Rawhide-Xfce-Live-715.iso