All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Moeller <marm.mm@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: LZO configure failure
Date: Fri, 17 Mar 2006 22:37:53 +0100	[thread overview]
Message-ID: <20060317213753.GA498@t-online.de> (raw)
In-Reply-To: <437e81e00603160720m1da949x@mail.gmail.com>

Hi,

I guess you have installed the LZO Library in /usr/local/lib.
The script ignores this library search path (like the most one).
Try to add it yourself as parameter to your configure script:

# ./configure BUILD_LDDFLAGS=-L/usr/local/lib
(tested with grub-1.91, also on FreeBSD 5.3)

On Thu, Mar 16, 2006 at 07:20:02AM -0800, Z3tbl4 [] wrote:
> Hello. Can anyone help me compile grub2 with LZO on FBSD 5.3 !
> I have lzo already installed. here is the configure output, thank you.
> 
> [zm@q] /usr/src/grub-1.92 # ./configure
> checking build system type... i386-unknown-freebsd5.3
> checking host system type... i386-unknown-freebsd5.3
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking for bison... bison -y
> checking for bison -y... (cached) bison -y
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for _LARGE_FILES value needed for large files... no
> checking whether optimization for size works... yes
> checking whether -falign-loops works... yes
> checking if C symbols get an underscore after compilation... no
> checking if start is defined by the compiler... no
> checking if _start is defined by the compiler... yes
> checking if __bss_start is defined by the compiler... yes
> checking if edata is defined by the compiler... yes
> checking if _edata is defined by the compiler... yes
> checking if end is defined by the compiler... yes
> checking if _end is defined by the compiler... yes
> checking whether addr32 must be in the same line as the instruction... yes
> checking for .code16 addr32 assembler support... yes
> checking whether an absolute indirect call/jump must not be prefixed
> with an asterisk... no
> checking if GCC has the regparm=3 bug... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether make sets $(MAKE)... yes
> checking for objcopy... objcopy
> checking whether objcopy works for absolute addresses... yes
> checking for strip... strip
> checking for nm... nm
> checking for ld... ld
> checking for ruby... no
> checking whether byte ordering is bigendian... no
> checking how to run the C preprocessor... gcc -E
> checking for egrep... grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for void *... yes
> checking size of void *... 4
> checking for long... yes
> checking size of long... 4
> checking for __lzo_init_v2 in -llzo2... no
> checking for __lzo_init_v2 in -llzo... no
> checking for __lzo_init2 in -llzo... no
> configure: error: LZO library version 1.02 or later is required
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2006-03-17 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16 15:20 LZO configure failure Z3tbl4 []
2006-03-17 21:37 ` Martin Moeller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-20 22:32 Lzo " xi yang
2006-03-20 22:51 ` Gregg C Levine
2006-03-21 20:57   ` Yoshinori K. Okuji
2006-03-22  0:29     ` Brian Sammon

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=20060317213753.GA498@t-online.de \
    --to=marm.mm@t-online.de \
    --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.