From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] snort: fix build on sparc v8
Date: Sun, 13 May 2018 15:55:32 +0200 [thread overview]
Message-ID: <20180513135532.GA22130@scaer> (raw)
In-Reply-To: <20180510111748.26293-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2018-05-10 13:17 +0200, Fabrice Fontaine spake thusly:
> Add patch to remove -mcpu=v9 before checking sparc architecture
>
> Fixes:
> - http://autobuild.buildroot.net/results/59625daa154e3136171dcb89bdc3b8b31dc85021
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> package/snort/0005-fix-sparc.patch | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 package/snort/0005-fix-sparc.patch
>
> diff --git a/package/snort/0005-fix-sparc.patch b/package/snort/0005-fix-sparc.patch
> new file mode 100644
> index 0000000000..14792d2c59
> --- /dev/null
> +++ b/package/snort/0005-fix-sparc.patch
> @@ -0,0 +1,28 @@
> +When checking if the architecture supports the %time register
> +instruction, do not force -mcpu to v9 while doing so. Otherwise it's
> +like "let's see if this v9 instruction exists when I force the compiler
> +to think I'm using v9", which is non-sensical.
> +
> +Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> +
> +diff -Naurp ./snort-2.9.11.1-orig/configure.in snort-2.9.11.1/configure.in
> +--- ./snort-2.9.11.1-orig/configure.in 2018-05-10 12:20:19.253510678 +0200
> ++++ snort-2.9.11.1/configure.in 2018-05-10 12:40:18.547584998 +0200
I was goign to request a git-formatted patch, but snort-2 is not
maintained in the open... Only snort-3 is on github...
Regards,
Yann E. MORIN.
> +@@ -942,8 +942,6 @@ fi
> +
> + # check for sparc %time register
> + if eval "echo $host_cpu|grep -i sparc >/dev/null"; then
> +- OLD_CFLAGS="$CFLAGS"
> +- CFLAGS="$CFLAGS -mcpu=v9 "
> + AC_MSG_CHECKING([for sparc %time register])
> + AC_RUN_IFELSE(
> + [AC_LANG_PROGRAM(
> +@@ -957,8 +955,6 @@ if eval "echo $host_cpu|grep -i sparc >/
> + AC_MSG_RESULT($sparcv9)
> + if test "x$sparcv9" = "xyes"; then
> + AC_DEFINE([SPARCV9],[1],[For sparc v9 with %time register])
> +- else
> +- CFLAGS="$OLD_CFLAGS"
> + fi
> + fi
> +
> --
> 2.14.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-05-13 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 11:17 [Buildroot] [PATCH 1/1] snort: fix build on sparc v8 Fabrice Fontaine
2018-05-13 13:55 ` Yann E. MORIN [this message]
2018-05-13 19:45 ` Thomas Petazzoni
2018-05-14 16:56 ` Sergio Prado
2018-05-15 12:41 ` Thomas Petazzoni
2018-05-15 14:28 ` Sergio Prado
2018-05-15 14:59 ` Fabrice Fontaine
2018-05-15 15:14 ` Thomas Petazzoni
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=20180513135532.GA22130@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.