All of lore.kernel.org
 help / color / mirror / Atom feed
* LZO configure failure
@ 2006-03-16 15:20 Z3tbl4 []
  2006-03-17 21:37 ` Martin Moeller
  0 siblings, 1 reply; 6+ messages in thread
From: Z3tbl4 [] @ 2006-03-16 15:20 UTC (permalink / raw)
  To: grub-devel

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: LZO configure failure
  2006-03-16 15:20 LZO " Z3tbl4 []
@ 2006-03-17 21:37 ` Martin Moeller
  0 siblings, 0 replies; 6+ messages in thread
From: Martin Moeller @ 2006-03-17 21:37 UTC (permalink / raw)
  To: The development of GRUB 2

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Lzo configure failure.
@ 2006-03-20 22:32 xi yang
  2006-03-20 22:51 ` Gregg C Levine
  0 siblings, 1 reply; 6+ messages in thread
From: xi yang @ 2006-03-20 22:32 UTC (permalink / raw)
  To: The development of GRUB 2

hi:
Try Lzo-1.08.tar.gz
I have got the same problem whem i was compiling the grub1.92 with Lz0-2,02
then I used Lzo-1.08.tar.gz,everything 's fine

BTW,you should enable the /usr/loacal/lib while lib searching

2006/3/20, Z3tbl4 [] <z3tbl4@gmail.com>:
> Thank you for your answer.
> i had some errors with includes which i fixed with this flags and
> copyind LZO includes to grub2 ./includes
>
> ./configure BUILD_LDDFLAGS=-L/usr/local/lib
> BUILD_CPPFLAGS=-I/usr/local/include BUILD_CFLAGS=-I/usr/local/include
>
> but now i can't compile with this error
>
> gcc -Iutil/i386/pc -I./util/i386/pc -I. -Iinclude -I./include -Wall -W
> -DGRUB_DATADIR=\"/usr/local/share/grub/i386-pc\" -g -O2 -DGRUB_UTIL=1
> -c -o grub_mkimage-util_i386_pc_grub_mkimage.o
> util/i386/pc/grub-mkimage.c
> In file included from util/i386/pc/grub-mkimage.c:27:
> include/grub/util/misc.h:41: error: syntax error before "off_t"
> include/grub/util/misc.h:45: error: syntax error before "off_t"
> gmake: *** [grub_mkimage-util_i386_pc_grub_mkimage.o] Error 1
>
> thank you
>
> 2006/3/18, grub-devel-request@gnu.org <grub-devel-request@gnu.org>:
> > Send Grub-devel mailing list submissions to
> >        grub-devel@gnu.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >        http://lists.gnu.org/mailman/listinfo/grub-devel
> > or, via email, send a message with subject or body 'help' to
> >        grub-devel-request@gnu.org
> >
> > You can reach the person managing the list at
> >        grub-devel-owner@gnu.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Grub-devel digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Re: LZO configure failure (Martin Moeller)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Fri, 17 Mar 2006 22:37:53 +0100
> > From: Martin Moeller <marm.mm@t-online.de>
> > Subject: Re: LZO configure failure
> > To: The development of GRUB 2 <grub-devel@gnu.org>
> > Message-ID: <20060317213753.GA498@t-online.de>
> > Content-Type: text/plain; charset=us-ascii
> >
> > 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
> >
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
> >
> > End of Grub-devel Digest, Vol 25, Issue 9
> > *****************************************
> >
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>



^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: Lzo configure failure.
  2006-03-20 22:32 Lzo configure failure xi yang
@ 2006-03-20 22:51 ` Gregg C Levine
  2006-03-21 20:57   ` Yoshinori K. Okuji
  0 siblings, 1 reply; 6+ messages in thread
From: Gregg C Levine @ 2006-03-20 22:51 UTC (permalink / raw)
  To: 'The development of GRUB 2'

Hello from Gregg C Levine
Actually libraries such as the LZO one belong in /usr/lib not
usr/local/lib (Note my correct spelling.) that might be most of
his/your problems. By instructing the configuration script where to
find or place your libraries you'll solve most of these problems.
These instructions are available by giving the configure script the
"--help" option, but without my quotes. Unless of course your building
Grub2 so that it will be placed in the /usr/local locations. 

The proper place for all libraries on Linux is indeed /usr/lib unless
the documentation insists upon it being otherwise. And of course your
not building your libraries on Linux but your building on one of the
BSDs.
---
Gregg C Levine hansolofalcon@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi 

> -----Original Message-----
> From: grub-devel-bounces+hansolofalcon=worldnet.att.net@gnu.org
[mailto:grub-
> devel-bounces+hansolofalcon=worldnet.att.net@gnu.org] On Behalf Of
xi yang
> Sent: Monday, March 20, 2006 5:33 PM
> To: The development of GRUB 2
> Subject: Lzo configure failure.
> 
> hi:
> Try Lzo-1.08.tar.gz
> I have got the same problem whem i was compiling the grub1.92 with
Lz0-2,02
> then I used Lzo-1.08.tar.gz,everything 's fine
> 
> BTW,you should enable the /usr/loacal/lib while lib searching
> 
> 2006/3/20, Z3tbl4 [] <z3tbl4@gmail.com>:
> > Thank you for your answer.
> > i had some errors with includes which i fixed with this flags and
> > copyind LZO includes to grub2 ./includes
> >
> > ./configure BUILD_LDDFLAGS=-L/usr/local/lib
> > BUILD_CPPFLAGS=-I/usr/local/include
BUILD_CFLAGS=-I/usr/local/include
> >
> > but now i can't compile with this error
> >
> > gcc -Iutil/i386/pc -I./util/i386/pc -I. -Iinclude -I./include
-Wall -W
> > -DGRUB_DATADIR=\"/usr/local/share/grub/i386-pc\" -g -O2
-DGRUB_UTIL=1
> > -c -o grub_mkimage-util_i386_pc_grub_mkimage.o
> > util/i386/pc/grub-mkimage.c
> > In file included from util/i386/pc/grub-mkimage.c:27:
> > include/grub/util/misc.h:41: error: syntax error before "off_t"
> > include/grub/util/misc.h:45: error: syntax error before "off_t"
> > gmake: *** [grub_mkimage-util_i386_pc_grub_mkimage.o] Error 1
> >
> > thank you
> >
> > 2006/3/18, grub-devel-request@gnu.org
<grub-devel-request@gnu.org>:
> > > Send Grub-devel mailing list submissions to
> > >        grub-devel@gnu.org
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > >        http://lists.gnu.org/mailman/listinfo/grub-devel
> > > or, via email, send a message with subject or body 'help' to
> > >        grub-devel-request@gnu.org
> > >
> > > You can reach the person managing the list at
> > >        grub-devel-owner@gnu.org
> > >
> > > When replying, please edit your Subject line so it is more
specific
> > > than "Re: Contents of Grub-devel digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > >   1. Re: LZO configure failure (Martin Moeller)
> > >
> > >
> > >
----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Fri, 17 Mar 2006 22:37:53 +0100
> > > From: Martin Moeller <marm.mm@t-online.de>
> > > Subject: Re: LZO configure failure
> > > To: The development of GRUB 2 <grub-devel@gnu.org>
> > > Message-ID: <20060317213753.GA498@t-online.de>
> > > Content-Type: text/plain; charset=us-ascii
> > >
> > > 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
> > >
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > Grub-devel mailing list
> > > Grub-devel@gnu.org
> > > http://lists.gnu.org/mailman/listinfo/grub-devel
> > >
> > >
> > > End of Grub-devel Digest, Vol 25, Issue 9
> > > *****************************************
> > >
> >
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Lzo configure failure.
  2006-03-20 22:51 ` Gregg C Levine
@ 2006-03-21 20:57   ` Yoshinori K. Okuji
  2006-03-22  0:29     ` Brian Sammon
  0 siblings, 1 reply; 6+ messages in thread
From: Yoshinori K. Okuji @ 2006-03-21 20:57 UTC (permalink / raw)
  To: The development of GRUB 2

On Monday 20 March 2006 23:51, Gregg C Levine wrote:
> Actually libraries such as the LZO one belong in /usr/lib not
> usr/local/lib (Note my correct spelling.) that might be most of
> his/your problems.

It is interesting when this changed. In the past, the standard location for 
add-on packages were always /usr/local, even with GNU/Linux.

Okuji



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Lzo configure failure.
  2006-03-21 20:57   ` Yoshinori K. Okuji
@ 2006-03-22  0:29     ` Brian Sammon
  0 siblings, 0 replies; 6+ messages in thread
From: Brian Sammon @ 2006-03-22  0:29 UTC (permalink / raw)
  To: The development of GRUB 2

> > Actually libraries such as the LZO one belong in /usr/lib not
> > usr/local/lib (Note my correct spelling.) that might be most of
> > his/your problems.
> 
> It is interesting when this changed. In the past, the standard location for 
> add-on packages were always /usr/local, even with GNU/Linux.

I don't really think it has.  As I've understood it, the convention is that 
libraries that are installed from the distribution go in /usr/lib, and 
libraries that are installed from source or from external archives of binary 
packages should go in /usr/local/lib/.

The FHS (http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY) 
while
a little vague on a few points[1], seems to support my understanding.

[1] Since they aren't defined in the spec, there may be some disagreement 
about what "locally installed" or "software" means.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-03-22  0:29 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-20 22:32 Lzo configure failure 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
  -- strict thread matches above, loose matches on Subject: below --
2006-03-16 15:20 LZO " Z3tbl4 []
2006-03-17 21:37 ` Martin Moeller

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.