On Fri, Mar 18, 2022 at 01:57:39AM -0500, Glenn Washburn wrote:
[...]
> Actually, with your help, I figured out how to not have to exclude windows
> builds, although I can only build test it.
I think that is enough for now. We can think about testing later...
Daniel
On Tue, Mar 15, 2022 at 02:36:12PM -0500, Glenn Washburn wrote:
> On Tue, 15 Mar 2022 14:23:48 +0100
> Daniel Kiper wrote:
>
> > On Fri, Mar 11, 2022 at 12:09:58AM +0100, Daniel Kiper wrote:
> > > On Wed, Mar 09, 2022 at 02:25:28PM -0600, Glenn Washburn wrote:
> > > > On Wed, 9 Mar 2022 16:49:57
On Fri, Mar 11, 2022 at 12:09:58AM +0100, Daniel Kiper wrote:
> On Wed, Mar 09, 2022 at 02:25:28PM -0600, Glenn Washburn wrote:
> > On Wed, 9 Mar 2022 16:49:57 +0100
> > Daniel Kiper wrote:
> >
> > > On Wed, Mar 02, 2022 at 06:25:12PM -0600, Glenn Washburn wrote:
> > > > Add linker flags when
On Wed, Mar 09, 2022 at 02:25:28PM -0600, Glenn Washburn wrote:
> On Wed, 9 Mar 2022 16:49:57 +0100
> Daniel Kiper wrote:
>
> > On Wed, Mar 02, 2022 at 06:25:12PM -0600, Glenn Washburn wrote:
> > > Add linker flags when linking kernel.exec to have malloc and free point to
> > > grub_malloc and
On Wed, 9 Mar 2022 16:49:57 +0100
Daniel Kiper wrote:
> On Wed, Mar 02, 2022 at 06:25:12PM -0600, Glenn Washburn wrote:
> > Add linker flags when linking kernel.exec to have malloc and free point to
> > grub_malloc and grub_free respectively. Some gdb functionality depends on
> > gdb locating
On Wed, Mar 02, 2022 at 06:25:12PM -0600, Glenn Washburn wrote:
> Add linker flags when linking kernel.exec to have malloc and free point to
> grub_malloc and grub_free respectively. Some gdb functionality depends on
> gdb locating the symbols "malloc" and "free", such as dynamically creating
>
