grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org, cyrille.lefevre-lists@laposte.net
Subject: Re: grub2-rc1-emu under cygwin
Date: Fri, 18 Oct 2013 01:10:19 +0200	[thread overview]
Message-ID: <52606E5B.2090309@gmail.com> (raw)
In-Reply-To: <510AEE21.20104@laposte.net>

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

Additional response to this older thread, now that few things changed.
> CC=gcc-4 ./configure --with-platform=emu --enable-grub-emu-usb
> --enable-grub-emu-sdl
> 
--enable-grub-emu-usb doesn't work. It's not important enough to fix it
given large amount of work it needs and not so useless as to remove it
alltogether.
> and the make command :
> 
> make -j 1 -k
> 
> -j 1 is to avoid fork failures.
> 
> what's wrong is :
> 
> cat syminfo.lst | sort | awk -f ./genmoddep.awk > moddep.lst || (rm -f
> moddep.lst; exit 1)
> __imp__CloseHandle@4 in emunet is not defined
> __imp__CreateEventA@16 in emunet is not defined
> __imp__CreateFileA@28 in emunet is not defined
> __imp__DeviceIoControl@32 in emunet is not defined
> __imp__GetLastError@0 in emunet is not defined
> __imp__GetOverlappedResult@16 in emunet is not defined
> __imp__ReadFile@20 in emunet is not defined
> __imp__RegCloseKey@4 in emunet is not defined
> __imp__RegEnumKeyExA@32 in emunet is not defined
> __imp__RegOpenKeyExA@20 in emunet is not defined
> __imp__RegQueryValueExA@24 in emunet is not defined
> __imp__ResetEvent@4 in emunet is not defined
> __imp__WaitForSingleObject@8 in emunet is not defined
> __imp__WriteFile@20 in emunet is not defined
> _cygwin_attach_handle_to_fd in emunet is not defined
> _get_osfhandle in emunet is not defined
> Makefile:81312: recipe for target `moddep.lst' failed
> 
I moved now this part to grub-devel/osdep/*/emunet.c. There is no
problem to access host functions anymore. Now it should be as easy
implementing grub-devel/osdep/windows/emunet.c and registering it in
grub-devel/osdep/emunet.c.
However some of the code you copied isn't license-compatible (namely it
states GPLv2-only), other files lack copyright headers altogether.
Copying files from external projects for secondary objectives isn't well
accepted in GNU projects under best of times. In case of copyright
problem like here it's a no-go in any project.
You can try clear-up the copyright situation by e.g. asking authors to
relicense tap-win32.h or rewriting it. However it still doesn't feel
important enough to grant an exception to guideline regarding regarding
external code.
How difficult is it to use the kernel driver without copying any code?


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

      parent reply	other threads:[~2013-10-17 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 22:20 grub2-rc1-emu under cygwin Cyrille Lefevre
2013-02-07  2:06 ` does grub-emu is supposed to build right ? (was Re: grub2-rc1-emu under cygwin) Cyrille Lefevre
2013-02-07  9:14   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-03 14:28 ` grub2-rc1-emu under cygwin Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-17 23:10 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=52606E5B.2090309@gmail.com \
    --to=phcoder@gmail.com \
    --cc=cyrille.lefevre-lists@laposte.net \
    --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).