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: Mon, 12 Apr 2010 16:39:01 +0200	[thread overview]
Message-ID: <106365637710330@192.168.2.69> (raw)
In-Reply-To: <4BC3247E.4000605@zetam.org>

Hi,

> when i've tried to compile xorriso on MacOSX 10.6.2
> i have this error during
> the link:
> Undefined symbols:
>  "_history_list", referenced from:
>       _Xorriso_status in xorriso_xorriso-xorriso.o
> ...
> If i add #undef Xorriso_with_readlinE to xorriso.c, i can compile it.

It looks as if the installed libreadline
does not provide function history_list().
I will try to add a check for this to the
configure script.


There are options for ./configure by which one
can disable libreadline and some other extra
dependencies:
    --disable-libreadline
    --disable-zlib     avoid use of zlib functions like compress2()
    --disable-libacl   avoid use of ACL functions like acl_to_text()
    --disable-xattr    avoid use of xattr functions like listxattr()

They all get disabled automatically by configure
tests if the facility is missing at all.
But here we have a case were it is missing
only in part.
The ACL and xattr stuff is currently Linux-only.
One would probably need a system adapter layer
to make this available on other OSes.

Many thanks for giving xorriso a test.


Have a nice day :)

Thomas




  reply	other threads:[~2010-04-12 14:42 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 [this message]
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

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=106365637710330@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.