GNU gv - Bugs: bug #23896, case collision with src/GV and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #23896: case collision with src/GV and src/gv
Submitter: | Ryan Carsten Schmidt <ryandesign> | ||
Submitted: | Sun 20 Jul 2008 07:32:48 AM UTC | ||
Category: | Sources configuration | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | msteinbo |
Open/Closed: | Closed | Release: | None |
Sun 20 Jul 2008 10:06:57 AM UTC, comment #4: |
Markus Steinborn <msteinbo> |
Sun 20 Jul 2008 08:57:48 AM UTC, comment #3: Before reporting I did check that the issue remained with 3.6.5. I've now updated the port to that version.
|
Ryan Carsten Schmidt <ryandesign> |
Sun 20 Jul 2008 07:56:36 AM UTC, comment #2: Thank you for the bug report. As a quick hack, you can comment out the following lines in src/Makefile.am:
|
Markus Steinborn <msteinbo> |
Sun 20 Jul 2008 07:35:18 AM UTC, comment #1: Here is the thread on the macports-users mailing list about this issue:
|
Ryan Carsten Schmidt <ryandesign> |
Sun 20 Jul 2008 07:32:48 AM UTC, original submission:
When building gv on a case-sensitive filesystem I see that, after running "make", the src directory contains both "gv" (the gv binary) and "GV" (the config file copied from GV.ad).
|
Ryan Carsten Schmidt <ryandesign> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2008-09-25 | msteinbo | Status | Workaround available | Fixed | |
Open/Closed | Open | Closed | |||
2008-07-20 | msteinbo | Status | None | Workaround available | |
Assigned to | None | msteinbo |
Powered by Savane 3.13-4448.
Corresponding source code
Thanks for the detailed response. It it very valuable, as it is the first report that the new "setenv-code" is working (it is not needed on Linux, you see).
I am investigating for a better solution, but that may take some time. Ideas are welcome.