similar to: [PATCH] Makefile: don't fail during make install on non mingw platforms

Hi, I've tried to compile syslinux under mandriva, and the compilation always bails out because it hasn't created win32/syslinux.exe. As far as I understand, the build will work fine on a Windows / mingw installation, but not Linux. I've modified my Makefile to remove the win32/syslinux.exe from the build, and it now builds OK. This happened on 3.3.6 and also on 4.0pre.

with the recent move of the includes from linux' include/asm-$ARCH to arch/$ARCH/asm, klibc fails to compile, because the in-linux-header files include from asm/, but this is not in the header search path. e.g. against linux-2.6.27 arm: arm-iwmmx-linux-gnueabi-gcc -Wp,-MD,usr/klibc/.vsnprintf.o.d -nostdinc -iwithprefix include -Iusr/include/arch/arm -Iusr/include/bits32

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

Hi, first i?ve installed SuSE 9.1 with the default rpms (heimdal 0.9.1rc3, samba 3.0.2a with winbind). I?ve configured the system with winbind to the user accounts from my Win2003 Server. All this works always max. 1 day. After this day I can?t connect to my shares on the samba server. After this I upgraded to 3.0.11 with the RPMs from de.samba.org for SuSE. I installed this rpms but Winbind

In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,

Am 13.05.2013 16:16, schrieb Tom Stellard: > On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: >> Hello, >> >> a few days ago, I was trying to access the LLVM target registry via the >> LLVM-C interface. Unfortunately I can't seem to get some useful >> information out of it. >> >> Despite the fact that the following code is written in

On Sat, May 11, 2013 at 01:48:44PM +0200, Christian Budde wrote: > Hello, > > a few days ago, I was trying to access the LLVM target registry via the > LLVM-C interface. Unfortunately I can't seem to get some useful > information out of it. > > Despite the fact that the following code is written in Pascal, can you > please tell me if I have done something wrong here?

On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > In Syslinux 6.03-pre6: > > > > _ The txt/html/*.html files are currently created 3 times, one for > > each firmware. I think they should be created only once (under the > > main txt/html/ directory), just as the rest of the documentation is. > > In that case, the

You could probably pay $15-20 for a paul budde report with relatively accurate figures. www.budde.com.au (even if he does believe asterisk is a passing fad - hi Paul :) he's still one of the best telco resources in Australia. Telsyste might be another option. Cheers, Dean -----Original Message----- From: asterisk-users-bounces@lists.digium.com

I'm building on Debian (Woody) though I don't think that's relevant. Having found no build instructions, no configure script I decided on 'make' It worked, except the ls command showed some files were not built because there are old versions in the tarball. I tried 'make clean all' but still I have old files: ls -ltr kwdhash.gen version.gen ldlinux.bss ldlinux.sys

> In Syslinux 6.03-pre6: > > _ The txt/html/*.html files are currently created 3 times, one for > each firmware. I think they should be created only once (under the > main txt/html/ directory), just as the rest of the documentation is. > In that case, the <respective_firmware>/txt/html/ subdirectories > should not even be created. > > _ The bios/dosutil/

> On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > > > > In Syslinux 6.03-pre6: > > > > > > _ The txt/html/*.html files are currently created 3 times, one for > > > each firmware. I think they should be created only once (under the > > > main txt/html/ directory), just as the rest of the documentation

On 2019-4-13 8:45, Lu Wei wrote: > On 2019-4-13 4:23, C. Masloch via Syslinux wrote: >> MS-DOS 7.10 (first appearing in MSW 95 OSR2, later re-used in MSW 98 >> and 98 SE) and 8.00 (MSW Me, and MSW XP DOS boot diskettes) both >> support FAT32 equally well. >> >> MS-DOS 8.00 (without some patches that are around) only supports >> booting in DOS mode from

Hello, a few days ago, I was trying to access the LLVM target registry via the LLVM-C interface. Unfortunately I can't seem to get some useful information out of it. Despite the fact that the following code is written in Pascal, can you please tell me if I have done something wrong here? // initialize all targets / target information LLVMInitializeAllTargets; LLVMInitializeAllTargetInfos;

Hello all, I'm trying to install Gentoo 1.4 rc2 for the first time on my laptop - HP Omnibook 5700ctx, P166, 128 MB RAM which cannot boot from CD-ROM. Apparenty Gentoo doesn't have a boot disk making utility. It's said that I must use tomsrbt or a slackware boot disk but I have none of those. & someone on Gentoo mailing list pointed out that I should try syslinux, Ok,

Mr Anvin, is there a specific loading address used with the Syslinux bootsector (to load ldlinux.sys)? like msdos 0x70, freedos 0x60 we're trying to have a SYS program that can create bootsector for other OS's than FreeDOS only. not much luck though :( this way I'm trying to avoid the use of syslinux.exe/com (need the diskspace that it would save by not including this program) I

Hi, I've made several attempts to boot syslinux from the harddisk. I have a win 98 startdiskette with syslinux and copybs. I strictly follow the procedure in the syslinux documentation. Yet, the result of the boot is not that linux is starting. Instead, the Microsoft windows screen flashes for a couple of seconds and is then replaced by a Dos prompt. Syslinux is V2.04. The PC is an IBM Aptiva

I've recently purchased an SSD with the goal of having a portable MS-Windows installation, something which Windows 8's "Windows to Go" feature allows (install to, and boot/run from, USB flash device). Housing the SSD in an external Zalman VE300 case allows presenting ISO files as hardware CD/DVD/BD drive with inserted medium. Having the ISO files present, it's tempting

I have tested with 3.31 (does not broke /dev/null) and 3.35/3.36 that broke /dev/null I verify that /dev/null exist, then compile one of the target available on top Makefile and /dev/null no more exist. Example root:/usr/src/syslinux-3.36# cat /dev/null root:/usr/src/syslinux-3.36# make .depend Makefile:274: .depend: No such file or directory rm -f .depend for csrc in syslxmod.c gethostip.c ; do

I have a 2gig usb drive FAT formatted with 32K cluster I used syslinux 3.06 to create a boot sector so that I could boot Damn Small Linux, INSERT and memtest86. They are all working fine. I have a DOS bootable CD and have been following this guy's instructions... http://fuzzymunchkin.dyndns.org/tdot/usbkeyfob/index.php3 I used a WinXP floppy formatted with the 'make ms-dos bootdisc'