From: Thomas Schmitt via Grub-devel <grub-devel@gnu.org>
To: grub-devel@gnu.org
Cc: Thomas Schmitt <scdbackup@gmx.net>
Subject: How to test the git clone without "make install" ?
Date: Fri, 14 Jun 2024 16:16:38 +0200 [thread overview]
Message-ID: <14273315194362440938@scdbackup.webframe.org> (raw)
Hi,
on occasion of
https://savannah.gnu.org/bugs/index.php?65880
"heap-buffer-overflow in grub-mkrescue.c"
i try to get grub-mkrescue running from git.
My problem is that grub_util_get_pkglibdir() returns
/usr/local/lib/grub
and grub_util_get_pkgdatadir() returns
/usr/local/share/grub
which of course do not come with a Debian installation.
So grub-mkrescue produces only a very small ISO with no boot lures or
boot programs. Quite unrealistic for testing.
I was able to overcome this obstacle by
ln -s /usr/lib/grub /usr/local/lib/grub
ln -s /usr/share/grub /usr/local/share/grub
but i understand that now my grub-mkrescue actually copies the ISO content
from the Debian installation and not from the git clone.
The manual
https://www.gnu.org/software/grub/manual/grub-dev/grub-dev.html
does not give me a clue how i would get the /usr/local/*/grub
directories populated with the files made from the git clone.
I guess "make install" would do it for me, but i fear that this does
too many other things to the GRUB installation of my vanilla Debian.
In general i would prefer to keep the git files away from any system
directory.
So what can i do to make the files built from git available to
./grub-mkrescue built from git, without frankensteining my Debian 12 ?
Have a nice day :)
Thomas
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2024-06-14 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 14:16 Thomas Schmitt via Grub-devel [this message]
2024-06-14 15:17 ` How to test the git clone without "make install" ? Maximilian Stendler
2024-06-14 15:22 ` Vladimir 'phcoder' Serbinenko
2024-06-14 17:27 ` [Solved] " Thomas Schmitt via Grub-devel
2024-06-14 17:29 ` Vladimir 'phcoder' Serbinenko
2024-06-14 18:12 ` Thomas Schmitt via Grub-devel
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=14273315194362440938@scdbackup.webframe.org \
--to=grub-devel@gnu.org \
--cc=scdbackup@gmx.net \
/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.