diff options
| author | Ilya Zakharevich <ilya@math.ohio-state.edu> | 1996-12-20 18:25:30 -0500 |
|---|---|---|
| committer | Chip Salzenberg <chip@atlantic.net> | 1996-12-23 12:58:58 +1200 |
| commit | d97d40b5b09d6d89f9fc39d5d51be2de4320c77b (patch) | |
| tree | 387bfa8b479c7a25d61acf832b8e1be00ab18b86 /Configure | |
| parent | d5d19f97d6576ffac48d0c2effb023b2c6b4d2c2 (diff) | |
| download | perl-d97d40b5b09d6d89f9fc39d5d51be2de4320c77b.tar.gz | |
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>
Diffstat (limited to 'Configure')
| -rwxr-xr-x | Configure | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -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 |