[syslinux] Nested SYSLINUX configurations -- error using CONFIG directive

[Rich Mahn]

Gilles Espinasse <g.esp at free.fr> wrote:
> 
> ----- Original Message ----- 
> From: "Rich Mahn" <rich at lat.com>
> To: "H. Peter Anvin" <hpa at zytor.com>
> Cc: "For discussion of Syslinux and tftp-hpa" <syslinux at zytor.com>
> Sent: Tuesday, March 29, 2011 9:52 PM
> Subject: Re: [syslinux] Nested SYSLINUX configurations -- error using
> CONFIGdirective
> 
> 
> > H. Peter Anvin <hpa at zytor.com> wrote:
> > >> There seems to be an error using '..' in the append portion of the
> > >> CONFIG directive.
> > >
> > > This is a known bug in Syslinux 4.03.  It should be fixed in 4.04-pre14,
> > > but if it is not, please scream.
> > >
> > > -hpa
> > >
> > >
> > > -- 
> > > H. Peter Anvin, Intel Open Source Technology Center
> > > I work for Intel.  I don't speak on their behalf.
> >
> > This bug still exists in 4.04-pre12.  I can't get 4.04-pre13 or
> > 4.04-pre14 to run at all.  I get the message:
> >
> >   SYSLINUX 4.04_pre13 CHS Copyright (c) 1994-2011 H. Peter Avin et al
> >
> > and then nothing else.
> >
> Yes 4.04-pre13 and pre14 need recompilation as they were compiled with a new
> compiler that screw something.
> Compilation require nasm-2.07 or newer, a recent binutils (2.20 or 2.21
> should work)
> Use 'make spotless && make' instead of 'make installer'
> 
> If your compiler is hardened to default to pie code like gcc gentoo or arch,
> peek the upstream patch to fix gpxe compilation
> http://git.ipxe.org/ipxe.git/commitdiff/fe61f6d
> 
> Gilles

Ok.  I have successfully recompile 4.04-pre14.  The problem still exists.  Here's
another example:
in root:
LABEL dir1
   config dir1/config.cfg
   append dir1
LABEL non-existant dir2
   config dir2/config.cfg
   append dir2

in dir1
LABEL up
   config ../config.cfg
   append ..

directory structure:  /dir1/dir2 with no /dir2

startup syslinux in the root directory.
select dir1, menu in dir1 comes up.
selet up, menu in root comes up.

then select dir2.  menu in /dir1/dir2 comes up

somehow the "current working directory" doesn't seem to get
changed with ".." or any variant thereof.  But the config
file and the other items, such as kernel, initrd, etc come
from the correct directory