[syslinux] boot... round 2

[Ady]

> Hi,
> 
> poma wrote:
> > - "unsigned char c;" does not solve the problem
> > 
> > - "c >= 0 && c <= ' '" solves the problem for the current git
 
:D
[sarcasm]
Perhaps we should simply remove vesamenu, and the problem will go away :O
[/sarcasm]
:D
 
> 
> What the ... ?!?
> My proposal of "(c >= 0 ... )" was only made to avoid the need
> for a type change of variable "c".
> Both proposals should be equivalent ... on the first morning
> glimpse they still are.
> 
> 
> > > could not
> > > find a mail where you tell the compiler version which
> > > produces working binaries.
> 
> > I wrote it in this thread already, here I will repeat a reference for you:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1234653#c9
> 
> 4.9.2-5.fc22.
> I got about the same one. Debian 4.9.2-10.
> 
> Anybody can give me hints how to install gcc 5 as alternative
> compiler on a Debian 8.1 ? (I am still learning about my new
> system.)
> 
> 
> To poma:
> There must be a character between 128 and 255 (-128 to -1)
> in the SYSAPPEND strings which needs the "c >= 0" term to
> survive. Any idea what it could be in the light of the list
> in  com32/include/syslinux/sysappend.h  ?
> 
> To all:
> Any idea how to inspect those strings while booting or while
> an operating system is up ?
 
Maybe we should rather wait?

 https://bugzilla.redhat.com/show_bug.cgi?id=1234653#c15 
Quote:
"So, the fix is definitely in the commits between 6.03 and current git master 
somewhere"

FWIW, I am still against releasing 6.04-pre1 yet.

Regards,
Ady.
 
> 
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
>