[syslinux] Syslinux 5 Path Option.

[Matt Fleming]

On Wed, 2012-12-12 at 00:12 +1000, Michael D. Setzer II wrote:
> On 11 Dec 2012 at 13:30, Matt Fleming wrote:
> 
> Subject:        	Re: [syslinux] Syslinux 5 Path Option.
> From:           	Matt Fleming <matt at console-pimps.org>
> To:             	"Michael D. Setzer II" 
> <mikes at kuentos.guam.net>
> Copies to:      	Syslinux at zytor.com
> Date sent:      	Tue, 11 Dec 2012 13:30:14 +0000
> 
> > On Tue, 2012-12-11 at 12:55 +1000, Michael D. Setzer II wrote:
> > > I'm not seeing how to set this path option?
> > > Here is what I get using vesamenu.c32 as an example when 
> > > moved to a directory outside of the build. The current syslinux 4.06
> > > has all the files in the same directory which is at the root of the
> > > cd.
> > > 
> > > ldd vesamenu.c32
> > > 
> > > linux-gate.so.1 =>  (0xb77c5000)
> > > ../../com32/libutil/libutil_com.c32 => not found
> > > ../../com32/lib/libcom32.c32 => not found
> > > 
> > > readelf -d vesamenu.c32
> > > 
> > > Dynamic section at offset 0x635c contains 17 entries:
> > >   Tag        Type                         Name/Value
> > >  0x00000001 (NEEDED)                     Shared library: 
> > > [../../com32/libutil/libutil_com.c32]
> > >  0x00000001 (NEEDED)                     Shared library: 
> > > [../../com32/lib/libcom32.c32]
> > >  0x6ffffef5 (GNU_HASH)                   0x94
> > >  0x00000005 (STRTAB)                     0x830
> > >  0x00000006 (SYMTAB)                     0x200
> > >  0x0000000a (STRSZ)                      1199 (bytes)
> > >  0x0000000b (SYMENT)                     16 (bytes)
> > >  0x00000003 (PLTGOT)                     0x6458
> > >  0x00000002 (PLTRELSZ)                   552 (bytes)
> > >  0x00000014 (PLTREL)                     REL
> > >  0x00000017 (JMPREL)                     0x10a8
> > >  0x00000011 (REL)                        0xce0
> > >  0x00000012 (RELSZ)                      968 (bytes)
> > >  0x00000013 (RELENT)                     8 (bytes)
> > >  0x00000016 (TEXTREL)                    0x0
> > >  0x6ffffffa (RELCOUNT)                   70
> > >  0x00000000 (NULL)                       0x0
> > > 
> > > So where does one modify this new PATH setting? The 
> > > ../../com32 path is in plan text using hexedit to look at, and could
> > > be manually modified, but that wouldn't appear to be the best way to
> > > modify it, and would probable be an unwanted hack.
> > 
> > You can safely ignore the paths of these DT_NEEDED entries - they're
> > not used internally by Syslinux, only the final path component is
> > used, e.g. libcom32.c32.
> > 
> > I'll fix the paths in the DT_NEEDED entries in the future so that it's
> > less confusing.
> > 
> Have done some testing with a build tree were I replaced the 4.06 
> with the 5.00 files and all the c32 it needed. 
> 
> First time, it gave a message that ldlinux.c32 was missing, so 
> added that to the directory. 
> 
> Then it was able to display the menu, and it works mostly.
> hdt runs fine except it doesn't seem to find the pci.ids file as it 
> works using 4.06. It also works if I reboot to exit hdt, but if I exit it 
> will not go back to the menu. Gives message 
> Failed to load COM32 file vesamenu.c32

Can you please provide your config file so I can try and debug this?

-- 
Matt Fleming, Intel Open Source Technology Center