delta/syslinux.git/linux, branch syslinux-4.xx git.kernel.org: pub/scm/boot/syslinux/syslinux.git Makefiles: don't include *.tmp 2014-01-19T00:09:19+00:00 H. Peter Anvin hpa@zytor.com 2014-01-19T00:09:19+00:00 374a37434fa11bdc95e0bc243aadb7de36bbbf43 Since checkin: bd09a6d828fa Major Makefile cleanups; gcc 4.3.0 compatiblity ... we include *.tmp into the Makefiles as well as .*.d. This seems to have been a mistake in made when adding *.tmp to cleanup rules, probably using a sed script. This causes problems, because *.tmp files are generated by the gcc_ok macro and do not contain Makefile rules at all. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Since checkin:

bd09a6d828fa Major Makefile cleanups; gcc 4.3.0 compatiblity

... we include *.tmp into the Makefiles as well as .*.d.  This seems
to have been a mistake in made when adding *.tmp to cleanup rules,
probably using a sed script.

This causes problems, because *.tmp files are generated by the gcc_ok
macro and do not contain Makefile rules at all.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Add NTFS filesystem support to Linux and Windows installers 2011-09-07T07:19:05+00:00 Paulo Alcantara pcacjr@gmail.com 2011-07-05T21:32:51+00:00 b0ac906b283b428ba1c7f35fe1e71a84b3d3d9c6 Signed-off-by: Paulo Alcantara <pcacjr@gmail.com> 
Signed-off-by: Paulo Alcantara <pcacjr@gmail.com>
Add "make strip" target 2011-05-10T03:02:27+00:00 H. Peter Anvin hpa@zytor.com 2011-05-10T03:02:27+00:00 2613174223371677d0a701a69cb7468947940d65 Add a "make strip" target, to make doing the official build easier. We want the official build to have stripped binaries for size reasons, so do it right and make it an actual build target. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Add a "make strip" target, to make doing the official build easier.
We want the official build to have stripped binaries for size reasons,
so do it right and make it an actual build target.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
linux: remove debugging OPTFLAGS 2011-05-09T22:01:45+00:00 H. Peter Anvin hpa@linux.intel.com 2011-05-09T22:01:45+00:00 5b2d99e4726e98a69492f452c7e2a9cbce46c55d Remove debugging OPTFLAGS which really should have made it in. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> 
Remove debugging OPTFLAGS which really should have made it in.

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Merge remote-tracking branch 'mfleming/for-hpa/makefile-cleanup' 2011-04-26T08:18:18+00:00 H. Peter Anvin hpa@zytor.com 2011-04-26T08:18:18+00:00 d5b9f24567a26562ec1822235cbd08256b96c335 Resolved Conflicts: com32/hdt/Makefile com32/sysdump/Makefile Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Resolved Conflicts:
	com32/hdt/Makefile
	com32/sysdump/Makefile

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
syslinux: check --update option properly 2011-04-15T18:28:31+00:00 Paulo Alcantara pcacjr@gmail.com 2011-04-15T18:28:31+00:00 fa6d94a16234683002235bea6d333162ba292da8 Signed-off-by: Paulo Alcantara <pcacjr@gmail.com> 
Signed-off-by: Paulo Alcantara <pcacjr@gmail.com>
Makefile: Move Makefile fragments into mk/ 2011-04-07T16:59:11+00:00 Matt Fleming matt.fleming@linux.intel.com 2011-04-07T16:12:08+00:00 d7e6cfaa6a990eb8fe2eaabe7fad1d1c8367a7ee Move the MCONFIG files into a mk/ directory and give them more descriptive names. This is purely a cosmetic change to make the 'include' directives a bit more coherent by making it obvious exactly which MCONFIG file we're including. For example, in com32/lua/src/Makefile we exchange the line, include ../../MCONFIG for the much more comprehensible, include $(MAKEDIR)/com32.mk Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com> 
Move the MCONFIG files into a mk/ directory and give them more
descriptive names.

This is purely a cosmetic change to make the 'include' directives a
bit more coherent by making it obvious exactly which MCONFIG file
we're including. For example, in com32/lua/src/Makefile we exchange
the line,

	include ../../MCONFIG

for the much more comprehensible,

	include $(MAKEDIR)/com32.mk

Signed-off-by: Matt Fleming <matt.fleming@linux.intel.com>
extlinux, linux: Ignore --force in these installers 2010-07-20T03:34:04+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2010-07-20T03:34:04+00:00 a8ed766f8c4eea40906086228f10785745342694 Previous commits described this behaviour, but did not actually implement it. :) Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca> 
Previous commits described this behaviour, but did not
actually implement it. :)

Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca>
libinstaller: Add --mbr, --active, and --force options 2010-07-03T09:28:00+00:00 Shao Miller shao.miller@yrdsb.edu.on.ca 2010-07-03T07:47:25+00:00 591ab24b42b606caf4dabbb8bf33dbc421e8f005 In order to consolidate the installer option-parsing system, we add the --mbr (-m), --active (-a), and --force (-f) options from the DOS, Win32, and mtools installers to libinstaller. Since the -m and -a options are not currently valid for the Linux 'syslinux' and 'extlinux' installers, we add error messages to both of these. The -f option is allowed but does nothing for them. Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca> 
In order to consolidate the installer option-parsing system,
we add the --mbr (-m), --active (-a), and --force (-f)
options from the DOS, Win32, and mtools installers to
libinstaller.

Since the -m and -a options are not currently valid for the
Linux 'syslinux' and 'extlinux' installers, we add error
messages to both of these.  The -f option is allowed but
does nothing for them.

Signed-off-by: Shao Miller <shao.miller@yrdsb.edu.on.ca>
installers: handle asprintf() correctly 2010-07-02T16:39:18+00:00 H. Peter Anvin hpa@zytor.com 2010-07-02T16:39:18+00:00 cb88d31c15a2803950e81663e4d808a31ba4f8c0 It appears that the glibc version of asprintf() is braindamaged, and doesn't set the target pointer to NULL in the event of an error (only returns -1). Therefore we need to check the return value. Just in case someone else made the *opposite* error, also check the pointer. Bleh. The glibc documentation states that *BSD sets the pointer to NULL, but instead of following that, the glibc people put warn_unused_result on asprintf. Sigh. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
It appears that the glibc version of asprintf() is braindamaged, and
doesn't set the target pointer to NULL in the event of an error (only
returns -1).  Therefore we need to check the return value.  Just in
case someone else made the *opposite* error, also check the pointer.

Bleh.  The glibc documentation states that *BSD sets the pointer to
NULL, but instead of following that, the glibc people put
warn_unused_result on asprintf.  Sigh.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>