From: Jiri B <jirib@devio.us>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: bug-grub@gnu.org, The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [openbsd] 2.02-beta3: build fails - getroot.c:(.text+0x2b): undefined reference to `getrawpartition'
Date: Mon, 14 Mar 2016 14:19:57 -0400 [thread overview]
Message-ID: <20160314181957.GV17281@wolfman.devio.us> (raw)
In-Reply-To: <56E4FD87.1040009@gmail.com>
On Sun, Mar 13, 2016 at 08:41:27AM +0300, Andrei Borzenkov wrote:
> > Well, I see something went wrong now with compressing a file:
> >
> > $ tar tzvf /home/jirib/openbsd/packages/amd64/all/grub-2.02-beta3.tgz | grep lzma_decompress
> > -r-xr-xr-x 1 root bin 3904 Jan 1 1970 lib/grub/i386-pc/lzma_decompress.image
> > -r--r--r-- 1 root bin 134480024 Jan 1 1970 lib/grub/i386-pc/lzma_decompress.img
> >
> > It should not be 128MB, right? :)
> >
>
> No. Something went wrong with section addresses/offsets. Please test
> 2.02~beta2 - do you observe the same problem? Please upload
> lzma_decompress.image. Where obcopy comes from (obcopy --version)? What
> assembler is used?
$ objcopy -V
GNU objcopy 2.17
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
OpenBSD uses binutils-2.17 and it's not possible to update it just like that,
it's part of OS.
The file is available here: http://afterboot.cz/pub/lzma_decompress.img
> > I uploaded whole build log here: http://devio.us/~jirib/grub.txt (2.3MB)
> >
> >>> -find . -iname '*.[ch]' ! -ipath './grub-core/lib/libgcrypt-grub/*' ! -ipath './build-aux/*' ! -ipath './grub-core/lib/libgcrypt/src/misc.c' ! -ipath './grub-core/lib/libgcrypt/src/global.c' ! -ipath './grub-core/lib/libgcrypt/src/secmem.c' ! -ipath './util/grub-gen-widthspec.c' ! -ipath './util/grub-gen-asciih.c' |sort > po/POTFILES.in
> >>> +find . -iname '*.[ch]' ! -path './grub-core/lib/libgcrypt-grub/*' ! -path './build-aux/*' ! -path './grub-core/lib/libgcrypt/src/misc.c' ! -path './grub-core/lib/libgcrypt/src/global.c' ! -path './grub-core/lib/libgcrypt/src/secmem.c' ! -path './util/grub-gen-widthspec.c' ! -path './util/grub-gen-asciih.c' |sort > po/POTFILES.in
> >>> find util -iname '*.in' ! -name Makefile.in |sort > po/POTFILES-shell.in
> >>>
> >>
> >> Hmm ... we support building on Windows which is case insensitive. What
> >> are other options to compare full path name case insenstive?
> >
> > I can live with patching it. OpenBSD find doesn't have 'ipath' and IIUC
> > it's not POSIX requiremement, so I doubt it will be implemented.
> >
>
> Why did you need it initially? Normally it is needed only when building
> from GIT; tarball comes with generated files.
I built from git snapshot, I haven't seen any tarball for beta3.
> >>> Another thing - 'INSTALL' file says >= autoconf 2.60 is needed but
> >>> it is >= 2.62 otherwise there is:
> >>>
> >>> "error: possibly undefined macro: AS_ECHO"
> >>>
> >>
> >> Indeed. According to git log, AS_ECHO appeared first in 2.61a. What
> >> version you have?
> >
> > IIUC it was firstly available in "normal" autoconf release in 2.62.
> >
>
> This does not answer my question - what autoconf version your system
> ships with (i.e. - do we need to change configure.ac or simply update
> INSTALL)?
IMO it would be ok to update INSTALL file. I had following autoconf
versions:
autoconf-2.13p3
autoconf-2.52p5
autoconf-2.59p4
autoconf-2.60p4
autoconf-2.61p4
autoconf-2.62p1
autoconf-2.63p0
autoconf-2.65p0
autoconf-2.67p0
autoconf-2.68p0
autoconf-2.69p1
Thanks for help.
j.
next prev parent reply other threads:[~2016-03-14 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160312165742.GR17281@wolfman.devio.us>
2016-03-12 18:29 ` [openbsd] 2.02-beta3: build fails - getroot.c:(.text+0x2b): undefined reference to `getrawpartition' Andrei Borzenkov
2016-03-12 19:54 ` Jiri B
2016-03-13 5:41 ` Andrei Borzenkov
2016-03-14 18:19 ` Jiri B [this message]
2016-03-14 18:46 ` Andrei Borzenkov
2016-03-17 10:12 ` Jiri B
2016-03-17 15:54 ` Andrei Borzenkov
2016-03-17 16:04 ` Vladimir 'phcoder' Serbinenko
2016-03-17 16:07 ` Andrei Borzenkov
2016-03-17 20:56 ` Jiri B
2016-03-18 3:26 ` Andrei Borzenkov
2016-03-18 13:01 ` Jiri B
2016-03-18 16:53 ` Andrei Borzenkov
2016-03-18 19:48 ` Vladimir 'phcoder' Serbinenko
2016-03-22 10:31 ` Jiri B
2016-03-22 17:48 ` Andrei Borzenkov
2016-03-24 3:55 ` Andrei Borzenkov
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=20160314181957.GV17281@wolfman.devio.us \
--to=jirib@devio.us \
--cc=arvidjaar@gmail.com \
--cc=bug-grub@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).