Mail Archives: djgpp-workers/2000/08/11/13:36:33
> From: Jim Meyering <meyering AT ascend DOT com>
> Date: 11 Aug 2000 11:57:32 +0200
>
> | 1) When the configure script runs, it prints an error message from
> | `ln' (when it tests whether `lstat' dereferences a symlink with a
> | trailing slash). This is expected behavior, but it might alarm
> | users. I suggest either to redirect stderr to /dev/null or at
> | least mention the message in djgpp/README.
>
> Thanks for the report.
>
> Can you send the precise error, or better still, a patch
> so I don't have to think, er... dig, so much :-)
This is a DJGPP-specific problem, and it will go away in the next
DJGPP release, where symlink support will be introduced. So I don't
think we need to bother you with this, it's something we need to find
a temporary solution for DJGPP build alone.
But since you asked, the problem happens in this fragment of the
configure script:
if { (eval echo configure:7318: \"$ac_link\") >&5; (eval $ac_link) 2>&5; } &&
test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null; then
ac_cv_func_lstat_dereferences_slashed_symlink=yes
else
echo "configure: failed program was:" >&5
cat conftest.$ac_ext >&5
ac_cv_func_lstat_dereferences_slashed_symlink=no
fi
rm -f conftest*
fi
else
# If the `ln -s' command failed, then we probably don't even
# have an lstat function.
ac_cv_func_lstat_dereferences_slashed_symlink=no
fi
> | The patch to depcomp which fixes this is below. Jim, where
> | should I post it?
>
> autoconf AT gnu DOT org, soon please, since a long-awaited snapshot
> is due to be made soon.
I will send today or tomorrow.
> | Also, is \{0,1\} supported in all versions of
> | Sed?
>
> I'm almost positive that it's not portable.
Then what is the portable repacement for the ? operator (which isn't
part of the basic regexps, and therefore isn't supported by Sed)?
I will need to redo the patch, it seems...
> | 4) lib/Makefile.in has a rule to produce C files from Yacc grammar
> | sources. This rule will not work on plain MS-DOS, because file
> | names like y.tab.c are not allowed, and because the DJGPP port of
> | Yacc produces y_tab.c instead of y.tab.c when it runs on plain
> | DOS machine. This problem will pop up if someone edits
> | getdate.y, for example.
>
> Not an issue, imho. If people want to do development, they'd
> be much better off using Unix.
I was thinking about fixing bugs, not necessarily about development.
Thanks for the feedback.
- Raw text -