Re: Building Emacs from a new MinGW environment

[Dani Moncayo <dmoncayo@gmail.com>]

>> > If that doesn't work, perhaps PATH_DUMPLOADSEARCH has the wrong value
>> > (it comes from src/epaths.h).
>>
>> It's defined like this:
>>   #define PATH_DUMPLOADSEARCH "/home/dani/emacs/emacs.git/lisp"
>
> This is wrong, it should be the full Windows file name starting with a
> drive letter.  Looks like the epaths-force-w32 target in the top-level
> Makefile is not working correctly for some reason.  It should convert
> the value of srcdir into a Windows d:/foo/bar format, and then replace
> @SRC@ in nt/epaths.nt with that value.

I see, but alas, right now I don't know how to investigate this further.

>> and after looking at that node in the GDB manual, I created a file
>> ~/.gdbinit with this line:
>>   add-auto-load-safe-path C:\msys\home\dani
>>
>> That removes the warning issued by gdb at startup, but the "xtype" and
>> "xstring" commands remain unknown to gdb.  What am I doing wrong?
>
> I'd try this instead:
>
>   set auto-load safe-path c:/msys/home/dani
>
> (I always disable this nuisance by using "/" as the argument.)

I just tried that too.  The warning disappears, but the xtype/xstring
commands remain undefined.


It seems that today is not my day :(

-- 
Dani Moncayo