All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: Compilation error of xorriso on MacOSX
Date: Tue, 13 Apr 2010 18:37:28 +0200	[thread overview]
Message-ID: <106336843611168@192.168.2.69> (raw)
In-Reply-To: <4BC48E12.6070506@zetam.org>

Hi,

Yves Blusseau wrote:
> http://www.mail-archive.com/autoconf@gnu.org/msg13241.html
> there a VL_LIB_READLINE macro

Ahum. A whole family of libraries.
Not only libreadline but also libedit, and
libeditline. This can become as interesting as
the situation with iconv.
But to our luck, libreadline is only nice to
have, not essential as is iconv.

So i now rather run a test build of all the
desired libreadline functions and the <*.h>
files. If that fails, then i flatly disable
readline.
(acinclude.m4 : LIBBURNIA_ASSERT_READLINE)

The new configure test for suitable libreadline
is ready and uploaded as xorriso-0.5.3.tar.gz.
Version timestamp :  2010.04.13.154201
(or later)


> I will make a MacPorts file so that xorriso can be build without problems on
> OSX.

Please wait with publishing until version 0.5.4
gets released.
I am currently working through the list of
minor problems. This should be done within a
few days.
(In general version 0.X.even is for production
 whereas 0.X.odd is merry development. Next
 development cycle will be 0.5.4 and 0.5.5.)


Have a nice day :)

Thomas




      reply	other threads:[~2010-04-13 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 13:47 Compilation error of xorriso on MacOSX Yves Blusseau
2010-04-12 14:39 ` Thomas Schmitt
2010-04-13 11:53   ` Yves Blusseau
2010-04-13 12:18     ` Thomas Schmitt
2010-04-13 12:34       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-13 14:50         ` Thomas Schmitt
2010-04-13 15:30           ` Yves Blusseau
2010-04-13 16:37             ` Thomas Schmitt [this message]

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=106336843611168@192.168.2.69 \
    --to=scdbackup@gmx.net \
    --cc=grub-devel@gnu.org \
    /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.