grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Jiri B <jirib@devio.us>
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: Thu, 17 Mar 2016 18:54:36 +0300	[thread overview]
Message-ID: <56EAD33C.2020805@gmail.com> (raw)
In-Reply-To: <20160317101239.GY17281@wolfman.devio.us>

17.03.2016 13:12, Jiri B пишет:
> On Mon, Mar 14, 2016 at 09:46:20PM +0300, Andrei Borzenkov wrote:
>>>>> $ 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
>>>> [...]
>>>> No. Something went wrong with section addresses/offsets. Please test
>>>> 2.02~beta2 - do you observe the same problem? Please upload
>>
>> Did you test beta2?
> 
> Hi, sorry for delay. Yes I tried beta2, same result.
> 
>>>> 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.
>>> [...]
>>
>> I asked lzma_decompress.image, not img. img is too late.
> 
> I apologize, I missed valid filename. So here as lzma_decompress.image from beta3
> (as beta2 got same huge img file).
> 
> http://afterboot.cz/pub/lzma_decompress.image
> SHA256 (lzma_decompress.image) = 3968a35c3fc2570cf1a888179433f23a7319d104c8622c71e501f4ba6ca38308
> 

Well, your compiler managed to create shared library instead of
executable file:

bor@bor-Latitude-E5450:~$ LANG=C objdump -f Загрузки/lzma_decompress.image

Загрузки/lzma_decompress.image:     file format elf32-i386
architecture: i386, flags 0x00000050:
HAS_SYMS, DYNAMIC
start address 0x00008200

I get the same if I explicitly add -shared to linker flags.

Could you test with

./configure TARGET_LDFLAGS=-static


  reply	other threads:[~2016-03-17 15:54 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
2016-03-14 18:46         ` Andrei Borzenkov
2016-03-17 10:12           ` Jiri B
2016-03-17 15:54             ` Andrei Borzenkov [this message]
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=56EAD33C.2020805@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=bug-grub@gnu.org \
    --cc=grub-devel@gnu.org \
    --cc=jirib@devio.us \
    /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).