From: Ilya Zakharevich Date: Fri, 20 Dec 1996 23:25:30 +0000 (-0500) Subject: Configure on OS/2 X-Git-Tag: accepted/trunk/20130322.191538~38041^2~571 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d97d40b5b09d6d89f9fc39d5d51be2de4320c77b;p=platform%2Fupstream%2Fperl.git Configure on OS/2 Subject: Re: OFFSETOF Chip Salzenberg writes: > > According to Ilya Zakharevich: > > OFFSETOF conflicts with system headers under OS/2. Can the name be > > changed slightly? > > Okay; or, would it be okay to "#undef OFFSETOF" and redefine it? In this case the extensions would not be able to access "old-format" 16-bit functions. Not that I know any extension which tries to do this... What is bad with PERL_OFFSET? p5p-msgid: <199612202353.SAA05539@monk.mps.ohio-state.edu> private-msgid: <199612202325.SAA05505@monk.mps.ohio-state.edu> --- diff --git a/Configure b/Configure index d22b009..c5fe4a4 100755 --- a/Configure +++ b/Configure @@ -3911,6 +3911,8 @@ case "$libs" in : elif try=`./loc lib$thislib$lib_ext X $libpth`; $test -f "$try"; then : + elif try=`./loc $thislib$lib_ext X $libpth`; $test -f "$try"; then + : elif try=`./loc lib$thislib X $libpth`; $test -f "$try"; then : elif try=`./loc $thislib X $libpth`; $test -f "$try"; then @@ -9036,6 +9038,7 @@ main() printf("int\n"); else printf("long\n"); + fflush(stdout); exit(0); } EOM