On Sat, Aug 08, 2009 at 12:49:27AM -0400, Pavel Roskin wrote:
> On Fri, 2009-08-07 at 22:39 +0200, Robert Millan wrote:
>
> > I don't understand this. Why is a requirement to install GNU binutils
> > unreasonable, whereas a requirement to install objconv is not?
>
> Installing binutils can break
Bean wrote:
You could also check out my new object format at
http://github.com/bean123/grub, lib branch. It supports conversion of
pe/elf/mach-o object file to a grub specific format, so that you can
use native build tool in Linux/OSX/Windows, no need for linker and
converter. It also reduce comp
On Fri, 2009-08-07 at 15:46 +0200, Robert Millan wrote:
> Other maintainers, is it burdensome to any of you to include these binaries
> in official builds? I suppose it's not, since mingw32 packages are widely
> available, but it doesn't hurt to ask :-)
I would prefer not to do a binary build at
On Fri, 2009-08-07 at 22:39 +0200, Robert Millan wrote:
> I don't understand this. Why is a requirement to install GNU binutils
> unreasonable, whereas a requirement to install objconv is not?
Installing binutils can break the existing toolchain. Installing
objconv should not.
It's a good idea
On Fri, Aug 07, 2009 at 04:06:11PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Fri, Aug 7, 2009 at 4:01 PM, Vladimir 'phcoder'
> Serbinenko wrote:
> > On Fri, Aug 7, 2009 at 3:46 PM, Robert Millan wrote:
> >>
> >> Hi,
> >>
> >&
Hi,
You could also check out my new object format at
http://github.com/bean123/grub, lib branch. It supports conversion of
pe/elf/mach-o object file to a grub specific format, so that you can
use native build tool in Linux/OSX/Windows, no need for linker and
converter. It also reduce compile time
Vladimir 'phcoder' Serbinenko wrote:
If you see pe2elf as being too much of a burden we may switch to
objconv: http://www.agner.org/optimize/. It's already used in
conjunction with Apple Mach-O toolchain. It's not a GNU project but is
licensed under GPL.
Thanks for the hint, I will try objco
Robert Millan wrote:
I thought of a possible solution to the grub-pe2elf problem. It seems that
it is burdensome to produce ELF binaries on Windows, but building PE binaries
or even PE/win32 executables on GNU/Linux is not (thanks to Mingw32 toolchain
which is available on most distributions
On Fri, Aug 7, 2009 at 4:01 PM, Vladimir 'phcoder'
Serbinenko wrote:
> On Fri, Aug 7, 2009 at 3:46 PM, Robert Millan wrote:
>>
>> Hi,
>>
>> I thought of a possible solution to the grub-pe2elf problem. It seems that
>> it is burdensome to produce ELF bi
On Fri, Aug 7, 2009 at 3:46 PM, Robert Millan wrote:
>
> Hi,
>
> I thought of a possible solution to the grub-pe2elf problem. It seems that
> it is burdensome to produce ELF binaries on Windows, but building PE binaries
> or even PE/win32 executables on GNU/Linux is not
Hi,
I thought of a possible solution to the grub-pe2elf problem. It seems that
it is burdensome to produce ELF binaries on Windows, but building PE binaries
or even PE/win32 executables on GNU/Linux is not (thanks to Mingw32 toolchain
which is available on most distributions).
If building GRUB
On Tue, Aug 04, 2009 at 11:45:45PM +0200, Christian Franke wrote:
>
> I'm somewhat worried that these complaints are delayed by more than a year
I noticed by chance. We were talking about something else on IRC, when
Bean mentioned that objcopy has bug when converting from PE to ELF. Later
he poi
.
I agree...
I haven't seen any apology or explanation in this thread.
... but I will not apologize simply because I did not commit the
grub-pe2elf patch.
Yes, this is what worries me the most.
I'm somewhat worried that these complaints are delayed by more t
Robert Millan wrote:
I don't understand what you mean about a "Linux cross-compiler":
- Why a compiler? AFAICT, the problem here is assembly/linkage
rather than compiling. binutils should suffice.
Unfortunately this is not true:
Some assembly language directives generated by gcc d
s not perfect it
> > works. And I propose not to touch it until it gives any maintainance
> > or technical problem. When it does then we may consider dropping or
> > limiting cygwin support. Until then this discussion is a waste of time
> > (IMO)
>
> I agree that ther
On Mon, Aug 03, 2009 at 11:33:23AM +0200, Christian Franke wrote:
> >
> > There has to be more to it. I know you were using GRUB on Cygwin
> > before that commit. Was this kludge being used since the beginning?
>
> I'm using GRUB on Cygwin since 'somewhat' before I announced the first
> patch
ntainance
> or technical problem. When it does then we may consider dropping or
> limiting cygwin support. Until then this discussion is a waste of time
> (IMO)
I agree that there is no urgent need to remove grub-pe2elf (although the
issue might come up essentially). However, it's not s
o from 2008-03-30 was based on this
> private branch merged to 1.96+epsilon.
>
>
>> What are the other options?
>>
>
> I don't know.
>
> Waiting until someone fixes BFD or maintains a Linux cross-compiler
> package for Cygwin (which cannot be build OOTB, it
t know.
Waiting until someone fixes BFD or maintains a Linux cross-compiler
package for Cygwin (which cannot be build OOTB, it requires build steps
on Linux) may last until time_t wraps around and is IMO not an option
:-)
Even the isolation of grub-pe2elf in a separate package would not help
much, beca
y
>>>> are later forgotten or ignored. Bean, please can you provide some
>>>> explanation
>>>> on what happened?
>>>>
>>>> Also, I think this commit should be reverted (at least the part that adds
>>>> grub-pe2elf).
>
ommit should be reverted (at least the part that adds
grub-pe2elf).
I would regret this. Then you could also revert all my Cygwin related
additions (some also included in Bean's r1726) because these no longer
make much sense unless someone fixes BFD or maintains a ELF toolchain
;> Also, I think this commit should be reverted (at least the part that adds
>> grub-pe2elf).
>
> I would regret this. Then you could also revert all my Cygwin related
> additions (some also included in Bean's r1726) because these no longer
> make much sense unless someon
Hi Robert,
Robert Millan wrote:
On a recent discussion on IRC, Bean pointed out that grub-pe2elf is essentially
a workaround for a bug in objcopy.
It is essentially a limitation of BFD: The object format specific
backends are apparently not implemented such that conversion between
Hi,
On a recent discussion on IRC, Bean pointed out that grub-pe2elf is essentially
a workaround for a bug in objcopy.
Bean explained that this bug is quite obvious. It seems Christian sent them
a patch, but it hasn't been applied (I don't know if it was rejected, or just
ignored,
On Thu, 2009-06-11 at 17:01 +0100, Colin Watson wrote:
> Looks like a copy-and-paste job gone slightly wrong.
>
> Index: util/grub-pe2elf.c
Applied. Thank you!
By the way, I welcome contributions from Ubuntu, the first major distro
to adopt GRUB2!
--
Regards,
Pavel Roskin
__
(stderr, "Try ``grub-editenv --help'' for more information.\n");
+fprintf (stderr, "Try ``grub-pe2elf --help'' for more information.\n");
else
printf ("\
-Usage: grub-editenv [OPTIONS] input [output]\n\
+Usage: grub-pe2elf [OPTIONS] input [out
not found error in modules
>> generated by mingw. After examining the binary image, it seems that PE
>> would use short name even for symbol whose length is 8, therefore no
>> null character at the end. grub-pe2elf assume the name is
>> null-terminated, which could result i
> necessary null-terminated.
> >
> > Oh, I didn't know that. Where is it documented?
>
> Hi,
>
> Recently, I found some wired symbol not found error in modules
> generated by mingw. After examining the binary image, it seems that PE
> would use short name even for
it documented?
Hi,
Recently, I found some wired symbol not found error in modules
generated by mingw. After examining the binary image, it seems that PE
would use short name even for symbol whose length is 8, therefore no
null character at the end. grub-pe2elf assume the name is
null-terminated,
On Saturday 11 April 2009 18:29:00 Bean wrote:
> Hi,
>
> When symbol name is 8 or less, pe store it as short name, which is not
> necessary null-terminated.
Oh, I didn't know that. Where is it documented?
Regards,
Okuji
___
Grub-devel mailing list
Gru
Hi,
When symbol name is 8 or less, pe store it as short name, which is not
necessary null-terminated. This patch take that into account and
append a null character at the end.
diff --git a/util/grub-pe2elf.c b/util/grub-pe2elf.c
index d703d33..a2504d2 100644
--- a/util/grub-pe2elf.c
+++ b/util/gr
31 matches
Mail list logo
