Mail Archives: djgpp/2009/06/13/20:20:39
> From: LM <ml AT distasis DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 13 Jun 2009 09:32:19 -0700 (PDT)
>
> Any tips on porting if configure script was not intended for djgpp?
It's hard to give any general tips, as the problems are a hodgepodge
of minor issues. I suggest that you identify the lines in the script
that cause failures (use "set -x" and config.log to help you zero in
on the offenders), and post them here together with a description of
any error messages or failures that they cause. People who did this
job more than once will quickly recognize familiar problems and give
advice on working around them.
Alternatively, look at the diffs between the DJGPP-ported script and
the Unix original, and try to figure out why the changes were made.
> Rugxulo wrote:
> >"./configure CC=gcc AWK=gawk"
>
> Will give it a try, although I did try export 'CC=gcc' in the djgpp
> bash shell before running. Didn't seem to make a difference.
Like I said, "CC=gcc.exe AWK=gawk.exe" should work better.
> Eli Zaretskii wrote:
> >Windows XP does not need any Registry settings to support long file
> >names. The FAQ advice is for older Windows versions.
>
> Are you sure about this?
Quite sure. I run configure scripts on XP as a matter of habit, and
never needed to do anything in the Registry for long file names.
> Some of the programs I was trying would not
> build until I switched the registry setting over. I spent a couple of
> hours debugging and realized it was using the short file name instead
> of the long one at some point. When it truncated the long file name
> to 8.3, the tilde-number kept it from finding the file. As soon as I
> switched the registry setting, it was able to truncate to a meaningful
> short file name from the long file name in the script and find the
> files properly.
DJGPP programs do not need properly 8.3-truncated file names, because
DJGPP supports long file names on XP out of the box. Unless you have
set LFN=n in the environment that is.
- Raw text -