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. Is the version 5.00 actually released released, or is it just released for developers to play with. +----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes at kuentos.guam.net mailto:msetzerii at gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+ http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC at HOME CREDITS SETI 13416295.233487 | EINSTEIN 9305112.319852 ROSETTA 5539904.166756 | ABC 15581177.139740
On 12/10/2012 21:55, Michael D. Setzer II wrote:> I'm not seeing how to set this path option?It was mentioned in the announcement e-mail that Matt Fleming authored and that Ady recently referred to. It is documented in doc/syslinux.txt.> 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 >So if we forget about linux-gate.so.1 for a moment, it seems that you've identified two files that vesamenu.c32 depends on. On the media you're trying to actually boot, which directory is vesamenu.c32 in? Which directory/directories are these two files in?> > Is the version 5.00 actually released released, or is it just released > for developers to play with.It seems to be a release for all users and not just a development version. - Shao Miller
> 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. >_If_ : initial installation directory = current working directory = where all the cfg files are located = where all the *.c32 files are located then you are not supposed to need the PATH directive. At least, not in theory. The practice may still be a different thing.> So where does one modify this new PATH setting?This is a new directive. All directives are set in respective configuration files for each Syslinux variant (syslinux.cfg,...). I would suggest to take a look at syslinux.txt from the Syslinux official archive. If you haven't yet read the whole email thread about 5.00 *.c32 dependencies, I would suggest to take a look at it.> > Is the version 5.00 actually released released, or is it just released > for developers to play with. >Since you are in doubt, let's put it this way: is there any reason for you to use 5.00 and not 4.06? Regards, Ady.
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. -- Matt Fleming, Intel Open Source Technology Center
On 12/10/2012 06:55 PM, Michael D. Setzer II wrote:> > 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. >It's a bug, and I have a fix for it already. I hope to make a 5.01-pre1 and then do a 5.01 bug fix release soon, since Matt is on vacation. -hpa