Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
pike
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pikelang
pike
Commits
ba0a6544
Commit
ba0a6544
authored
22 years ago
by
Xavier Beaudouin
Browse files
Options
Downloads
Patches
Plain Diff
Another klundge for CygWin
Rev: src/configure.in:1.635
parent
79f7ebad
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/configure.in
+3
-2
3 additions, 2 deletions
src/configure.in
with
3 additions
and
2 deletions
src/configure.in
+
3
−
2
View file @
ba0a6544
AC_REVISION("$Id: configure.in,v 1.63
4
2002/10/0
7
1
5:42:28 grubba
Exp $")
AC_REVISION("$Id: configure.in,v 1.63
5
2002/10/0
9
1
0:03:16 kiwi
Exp $")
AC_INIT(interpret.c)
AC_CONFIG_HEADER(machine.h)
...
...
@@ -622,10 +622,11 @@ fi
case "$pike_cv_sys_os" in
CYGWIN*)
echo 'Cygwin host detected. Enabling workarounds...'
# winsock.h, winbase.h, winsock2.h, windows.h, wingdi.h
# winsock.h, winbase.h, winsock2.h, windows.h, wingdi.h
, windef.h
# are part of VC api but given as headers in cygwin. We
# should detect them when using cygwin
ac_cv_header_wingdi_h="no"
ac_cv_header_windef_h="no"
ac_cv_header_winsock_h="no"
ac_cv_header_winsock2_h="no"
ac_cv_header_winbase_h="no"
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment