#15339 closed defect (fixed)
gf2x tuning process needs to execute update-thresholds which needs a manifest file on Cygwin
| Reported by: | jpflori | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
| Component: | porting: Cygwin | Keywords: | cygwin spkg gf2x |
| Cc: | kcrisman, dimpase, tscrim | Merged in: | |
| Authors: | Reviewers: | Jean-Pierre Flori, Travis Scrimshaw | |
| Report Upstream: | Reported upstream. No feedback yet. | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Description (last modified by )
This used to be true on Windows 7+ at least, same problem for any exe whose name contains patch/install/update...
As this one happens during gf2x building process and Windows is particularly picky about timestamps of the exe and the corresponding manifest file, this will not be completely trivial to fix. i.e. we have to patch gf2x build system (or convince them to change the exe name... I'll report there shortly).
Attachments (1)
Change History (19)
comment:1 Changed 5 years ago by
- Cc kcrisman tscrim added
- Dependencies set to #15316
- Keywords cygwin spkg gf2x added
comment:2 Changed 5 years ago by
- Branch set to u/jpflori/ticket/15339
- Report Upstream changed from N/A to Reported upstream. No feedback yet.
- Status changed from new to needs_review
comment:3 Changed 5 years ago by
- Commit set to d0512bb672bbf7bfde03e0156e00396c8ec64669
comment:4 Changed 5 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:5 Changed 4 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:6 Changed 4 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:7 Changed 4 years ago by
I suggest we just don't tune on Windows >= 7 till gf2x does something upstream.
comment:8 Changed 4 years ago by
Or do nothing, my latest tests were fine and Windows 7 just let update-thresholds.sh be executed without ranting.
comment:9 Changed 4 years ago by
@Travis: can you confirm that update-thresholds now executes without trouble (if your Windows version is >=7 and recent enough)?
comment:10 Changed 4 years ago by
I believe my gf2x built on cygwin32 (I'm running Win8), which is sufficient, right? I'll double-check later today.
Changed 4 years ago by
comment:11 Changed 4 years ago by
1.1.p1 built successfully for me and I've attached the log in case there is something in there you (or if you tell me, I) need to look for.
comment:12 Changed 4 years ago by
- Branch u/jpflori/ticket/15339 deleted
- Commit d0512bb672bbf7bfde03e0156e00396c8ec64669 deleted
- Dependencies #15316 deleted
- Description modified (diff)
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Reviewers set to Jean-Pierre Flori, Travis Scrimshaw
- Status changed from needs_review to positive_review
Everything is fine!
You have a ./update-thresholds -o tuned_thresholds.h < tunetoom.res and no errors.
comment:13 Changed 4 years ago by
- Resolution set to fixed
- Status changed from positive_review to closed
comment:14 Changed 4 years ago by
Strange, it now fails for me on Windows 7 64 bits under Cygwin32, but is ok under Cygwin64... And I re checked Travis log and there was no problem even if he was under Windows ? 64 bits under Cygwin32 !!!
comment:15 Changed 4 years ago by
It also fails for me in exactly the same situation (windows 7 64 bits, works with cygwin64, fails with cygwin32). Compiling as administrator solves the problem, but it is not very serious...
comment:16 Changed 4 years ago by
A more and less serious solution is to export SAGE_TUNE_GF2X=no, I'll let you guess what it does...
comment:17 Changed 4 years ago by
You can also disable UAC on Windows.
Whatsoever, we should maybe try to craft a manifest file for update-threshold.exe.
comment:18 Changed 4 years ago by
Follow up at #17861.
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
Let gf2x use --libdir and make SAGE_FAT_BINARY work.Replace symlink in a more portable way.Let gf2x tune on Cygwin64.Make generic build of gf2x smarter.More fixes for gf2x generic build.Support SSE2 on x86_64 for gf2x.Simplify generic build of gf2x.Properly autoreconfed patches.Document new gf2x patch.Prevent autotools to regenerate files.