Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 4/4] guile: new package
Date: Sun, 23 Nov 2014 16:29:36 +0100	[thread overview]
Message-ID: <20141123152936.GB4210@free.fr> (raw)
In-Reply-To: <546E72F4.5040103@paguilar.org>

Pedro, All,

On 2014-11-21 00:02 +0100, Pedro Aguilar spake thusly:
> On 18/11/2014 22:18, Yann E. MORIN wrote:
[--SNIP--]
> >>diff --git a/package/guile/guile-01-fix_arm_endianness.patch b/package/guile/guile-01-fix_arm_endianness.patch
> >>new file mode 100644
> >>index 0000000..a30a241
> >>--- /dev/null
> >>+++ b/package/guile/guile-01-fix_arm_endianness.patch
> >>@@ -0,0 +1,25 @@
> >>+Fix support for ARM endianness, otherwise it gives the error
> >>+"unknown CPU endianness"
> >>+
> >>+Signed-off-by: Pedro Aguilar <paguilar@paguilar.org>
> >
> >Did you try to send that patch upstream?
> 
> They already fixed it in git, but there isn't any stable release with this
> fix.

Ah, so this is a patch that you back-ported from upstream, then?

In this case, just add a pointer to the upstream patch.

> >>+diff -Nau guile-2.0.11.orig/configure.ac guile-2.0.11/configure.ac
> >>+--- guile-2.0.11.orig/configure.ac	2014-03-12 14:36:02.000000000 +0100
> >>++++ guile-2.0.11/configure.ac	2014-11-03 23:59:51.897267207 +0100
> >>+@@ -862,7 +862,7 @@
> >>+ }]])],
> >>+     [guile_cv_use_csqrt=yes],
> >>+     [guile_cv_use_csqrt="no, glibc 2.3 bug"],
> >>+-    [guile_cv_use_csqrt="yes, hopefully (cross-compiling)"])])
> >>++    [guile_cv_use_csqrt="no (cross-compiling)"])])
> >
> >Not OK: it is possible to be cross-compiling with glibc, in which
> >case the result should be 'yes'.
> 
> Using csqrt() is OK only for some versions of glib. If we use the fallback
> code, we're sure that it will work properly even with recent versions of
> glib.

/me gets confused...
glib or glibc?

But even if the fallback code works in all cases, I gues we still want
to use the normal code whenever possible. That is, we want to detect
that csqrt() is available before using it.

But OK, we can live with the fallback code in Buildroot.

Maybe you could try to push a patch upstream to add a check whether
csqrt() is present and useable in the C library? That would allow us to
drop one patch when we update guile when the next release is out.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-11-23 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 21:48 [Buildroot] [PATCH v4 0/4] package/guile: New package Pedro Aguilar
2014-11-06 21:48 ` [Buildroot] [PATCH v4 1/4] libatomic_ops: Add host-autotools-package Pedro Aguilar
2014-11-18 20:35   ` Yann E. MORIN
2014-11-06 21:48 ` [Buildroot] [PATCH v4 2/4] bdwgc: new package Pedro Aguilar
2014-11-18 20:59   ` Yann E. MORIN
2014-11-20 21:47     ` Pedro Aguilar
2014-11-23 15:23       ` Yann E. MORIN
2014-11-06 21:48 ` [Buildroot] [PATCH v4 3/4] libunistring: Add host-autotools-package Pedro Aguilar
2014-11-18 21:03   ` Yann E. MORIN
2014-11-06 21:48 ` [Buildroot] [PATCH v4 4/4] guile: new package Pedro Aguilar
2014-11-18 21:18   ` Yann E. MORIN
2014-11-20 23:02     ` Pedro Aguilar
2014-11-23 15:29       ` Yann E. MORIN [this message]
2014-11-23 19:20         ` Pedro Aguilar

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=20141123152936.GB4210@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox