Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/x86/syslinux
Date: Tue, 28 Nov 2006 02:01:46 -0800 (PST)	[thread overview]
Message-ID: <20061128100146.B0BCC48581@busybox.net> (raw)

Author: aldot
Date: 2006-11-28 02:01:46 -0800 (Tue, 28 Nov 2006)
New Revision: 16702

Log:
- look at target variants when determining if syslinux is supported or not.
  Closes #637


Modified:
   trunk/buildroot/target/x86/syslinux/syslinux.mk


Changeset:
Modified: trunk/buildroot/target/x86/syslinux/syslinux.mk
===================================================================
--- trunk/buildroot/target/x86/syslinux/syslinux.mk	2006-11-28 08:49:17 UTC (rev 16701)
+++ trunk/buildroot/target/x86/syslinux/syslinux.mk	2006-11-28 10:01:46 UTC (rev 16702)
@@ -1,4 +1,21 @@
+SYSLINUX_SUPPORTED_ARCH=n
 ifeq ($(ARCH),i386)
+SYSLINUX_SUPPORTED_ARCH=y
+endif
+ifeq ($(ARCH),i486)
+SYSLINUX_SUPPORTED_ARCH=y
+endif
+ifeq ($(ARCH),i586)
+SYSLINUX_SUPPORTED_ARCH=y
+endif
+ifeq ($(ARCH),i686)
+SYSLINUX_SUPPORTED_ARCH=y
+endif
+ifeq ($(ARCH),x86_64)
+SYSLINUX_SUPPORTED_ARCH=y
+endif
+ifeq ($(SYSLINUX_SUPPORTED_ARCH),y)
+
 #############################################################
 #
 # syslinux to make target msdos/iso9660 filesystems bootable

             reply	other threads:[~2006-11-28 10:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 10:01 aldot at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-02 19:21 [Buildroot] svn commit: trunk/buildroot/target/x86/syslinux jacmet at uclibc.org
2008-03-06 18:59 ninevoltz at uclibc.org
2008-02-18 22:10 thomasez at uclibc.org
2007-12-13 12:15 vanokuten at uclibc.org
2007-07-08 20:51 aldot at uclibc.org
2006-11-14 23:22 andersen at uclibc.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061128100146.B0BCC48581@busybox.net \
    --to=aldot@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox