All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: 64-bit UEFI build is broken
Date: Wed, 09 Nov 2011 10:00:23 +0100	[thread overview]
Message-ID: <4EBA4127.7000402@gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1111082210170.9801@oretfbsg>

[-- Attachment #1: Type: text/plain, Size: 2636 bytes --]

On 09.11.2011 07:17, Seth Goldberg wrote:
> Hi,
>
>   Just a followup -- it appears that the root cause is a missing
> "-m64" -- since the compilation for this platform should be done with
> -m64, the preprocessing done for .lst generation should also be done
> with that cflag, otherwise (at least in this case), the library gets
> confused.
>
>  Adding 'TARGET_CPPFLAGS=-m64" to the configure line allowed the build
> to finish without errors (though I'm not sure if that's the proper fix).
>  
You're right. This is the problem.
>
>  --S
>
> Quoting Seth Goldberg, who wrote the following on Tue, 8 Nov 2011:
>
>>
>> Latest trunk (Linux host, configured with "--target=x86_64
>> --with-platform=efi") stops while building btrfs:
>>
>> gcc -E -DGRUB_LST_GENERATOR -Dgrub_fs_register=FS_LIST_MARKER
>> -Dgrub_video_register=VIDEO_LIST_MARKER
>> -Dgrub_parttool_register=PARTTOOL_LIST_MARKER
>> -Dgrub_partition_map_register=PARTMAP_LIST_MARKER
>> '-Dgrub_term_register_input(...)=INPUT_TERMINAL_LIST_MARKER(__VA_ARGS__)'
>> '-Dgrub_term_register_output(...)=OUTPUT_TERMINAL_LIST_MARKER(__VA_ARGS__)'
>> '-Dgrub_register_command(...)=COMMAND_LIST_MARKER(__VA_ARGS__)'
>> '-Dgrub_register_extcmd(...)=EXTCOMMAND_LIST_MARKER(__VA_ARGS__)'
>> '-Dgrub_register_command_p1(...)=P1COMMAND_LIST_MARKER(__VA_ARGS__)'
>> -DHAVE_CONFIG_H -I. -I../../grub-core -I..  -Wall -W -I../../include
>> -I../include  -DGRUB_MACHINE_EFI=1 -DGRUB_MACHINE=X86_64_EFI
>> -nostdinc -isystem /usr/lib/gcc/i686-linux-gnu/4.6.1/include
>> -DGRUB_FILE=\"fs/btrfs.c\" -I. -I../../grub-core -I.. -I../..
>> -I../../include -I../include -I../../grub-core/lib/posix_wrap
>> -I../../grub-core/lib/minilzo -DMINILZO_HAVE_CONFIG_H  
>> ../../grub-core/fs/btrfs.c ../../grub-core/lib/crc.c
>>> btrfs.marker.new || (rm -f btrfs.marker; exit 1)
>> In file included from ../../grub-core/lib/minilzo/lzoconf.h:75:0,
>>                 from ../../grub-core/lib/minilzo/minilzo.h:60,
>>                 from ../../grub-core/fs/btrfs.c:29:
>> ../../grub-core/lib/minilzo/lzodefs.h:849:6: error: #error "this
>> should not happen"
>> make[3]: *** [btrfs.marker] Error 1
>>
>>
>>  It's not expecting sizeof(ulong_t) to exceed 32-bits.
>>
>> --S
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  parent reply	other threads:[~2011-11-09  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09  5:55 64-bit UEFI build is broken Seth Goldberg
2011-11-09  6:17 ` Seth Goldberg
2011-11-09  7:26   ` Lukas Anzinger
2011-11-09  9:00   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-09  9:09   ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-09 18:33     ` Seth Goldberg

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=4EBA4127.7000402@gmail.com \
    --to=phcoder@gmail.com \
    --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.