> > Emphasize proper NASM versions. > > --- > NEWS | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/NEWS b/NEWS > index d1a5b2c..7848c6b 100644 > --- a/NEWS > +++ b/NEWS > @@ -2,6 +2,10 @@ Starting with 1.47, changes marked with SYSLINUX, PXELINUX, ISOLINUX > or EXTLINUX apply to that specific program only; other changes apply > to all derivatives. > > +Changes in 6.04: > + * NASM 2.11.08 or later is required to build > + SYSLINUX from source. > + > Changes in 6.03: > * chain: Fix chainloading on 6.02 (Raphael S. Carvalho). > * core: Do not leak the __lowmem and __bss16 macros to modules;1_ The NEWS file would not be an adequate place to post such information, for several reasons. 2_ Expressing the problem with NASM in such a way would be very inaccurate. The problem is in NASM 2.11.06, and only in that version. The problem is not in Syslinux, and many other versions of NASM (such as 2.11.05) have no problem. As I already said multiple times (not just in the Syslinux Mailing List), this kind of information develops according to various circumstances, at different times, from different sources, and with no control nor influence from The Syslinux Project. Therefore, the adequate place for accurate information of this kind is a "Building" wiki page. Regards, Ady.
Or a README or something. I don't read the CHANGELOG before building, I read whatever constitutes the installation instructions. I guess I'd read an FAQ if it doesn't work (now that I think about it, rpmbuild doesn't work on the SPEC -- suppose I should report that separately). Sent from my iPhone On Mar 6, 2016, at 13:02, Ady via Syslinux <syslinux at zytor.com> wrote:>> >> Emphasize proper NASM versions. >> >> --- >> NEWS | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/NEWS b/NEWS >> index d1a5b2c..7848c6b 100644 >> --- a/NEWS >> +++ b/NEWS >> @@ -2,6 +2,10 @@ Starting with 1.47, changes marked with SYSLINUX, PXELINUX, ISOLINUX >> or EXTLINUX apply to that specific program only; other changes apply >> to all derivatives. >> >> +Changes in 6.04: >> + * NASM 2.11.08 or later is required to build >> + SYSLINUX from source. >> + >> Changes in 6.03: >> * chain: Fix chainloading on 6.02 (Raphael S. Carvalho). >> * core: Do not leak the __lowmem and __bss16 macros to modules; > > 1_ The NEWS file would not be an adequate place to post such > information, for several reasons. > > 2_ Expressing the problem with NASM in such a way would be very > inaccurate. The problem is in NASM 2.11.06, and only in that version. > The problem is not in Syslinux, and many other versions of NASM (such > as 2.11.05) have no problem. > > As I already said multiple times (not just in the Syslinux Mailing > List), this kind of information develops according to various > circumstances, at different times, from different sources, and with no > control nor influence from The Syslinux Project. Therefore, the > adequate place for accurate information of this kind is a "Building" > wiki page. > > Regards, > Ady. > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
> Or a README or something.When we pay attention to other documents in the Syslinux archives, this type of information is much more adequate for the wiki... There is now a modest starting point [1]. Let's hope, in time, developers that contribute to The Syslinux Project will actually add relevant information (conflicts, tips, recommended procedures... that are not appropriate for "./doc/building.txt". Regards, Ady. [1] http://www.syslinux.org/wiki/index.php/Building
On 03/06/16 10:02, Ady via Syslinux wrote:> > 1_ The NEWS file would not be an adequate place to post such > information, for several reasons. > > 2_ Expressing the problem with NASM in such a way would be very > inaccurate. The problem is in NASM 2.11.06, and only in that version. > The problem is not in Syslinux, and many other versions of NASM (such > as 2.11.05) have no problem. > > As I already said multiple times (not just in the Syslinux Mailing > List), this kind of information develops according to various > circumstances, at different times, from different sources, and with no > control nor influence from The Syslinux Project. Therefore, the > adequate place for accurate information of this kind is a "Building" > wiki page. >For the case of NASM 2.11.06, I just put a test into head.inc to make it error out. -hpa
On Tue, Mar 8, 2016 at 3:21 AM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote:> On 03/06/16 10:02, Ady via Syslinux wrote: >> >> 1_ The NEWS file would not be an adequate place to post such >> information, for several reasons. >> >> 2_ Expressing the problem with NASM in such a way would be very >> inaccurate. The problem is in NASM 2.11.06, and only in that version. >> The problem is not in Syslinux, and many other versions of NASM (such >> as 2.11.05) have no problem. >> >> As I already said multiple times (not just in the Syslinux Mailing >> List), this kind of information develops according to various >> circumstances, at different times, from different sources, and with no >> control nor influence from The Syslinux Project. Therefore, the >> adequate place for accurate information of this kind is a "Building" >> wiki page. >> > > For the case of NASM 2.11.06, I just put a test into head.inc to make it > error out. > > -hpaThere's also an issue with a newer keyword that started in NASM 2.03? If I recall, the clause in head.inc isn't seen soon enough to throw the error though looking back, it's been 5-1/2 years since I had mentioned it. -- -Gene