bugThe FreeType Project - Bugs: bug #26878, ftjam does not behave as expected...

 
 

bug #26878: ftjam does not behave as expected in cygwin

Submitted by:  Allen Farris <afarris>
Submitted on:  Wed 24 Jun 2009 04:25:41 PM UTC  
 
Severity:  3 - Normal Item Group:  Incorrect behaviour
Status:  Confirmed Privacy:  Public
Assigned to:  David Turner <freetype> Open/Closed:  Open
Planned Release:  None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 25 Jun 2009 05:49:55 PM UTC, comment #4:

Oops! You are right. I've assigned this to David; he has probably the patched sources which he can add to the CVS.

Werner LEMBERG <wl>
Project Administrator
Thu 25 Jun 2009 01:52:14 PM UTC, comment #3:

I haven't had a chance to test the patch yet but I did notice that where you put it (the CVS repository) isn't up to date. It is still based on perforce jam 2.3, not 2.5 (I guess you guys stopped using the CVS repository for a while?). An example of this can be seen here:

http://public.perforce.com:8080/@md=d&cd=//public/jam/src/&cdf=//public/jam/src/jamgram.yy&c=oOU@//public/jam/src/jamgram.yy?ac=98&rev1=13

http://cvs.savannah.gnu.org/viewvc/freetype/jam/jamgram.yy?hideattic=1&revision=1.1.1.1&view=markup

I suppose your best course of action if you want to fix this would be to download the source forge tar.gz and merge it with your CVS repository (or simply overwrite everything in CVS and remake the change). Package is at:

http://sourceforge.net/project/showfiles.php?group_id=3157&package_id=19789

Allen Farris <afarris>
Thu 25 Jun 2009 05:08:14 AM UTC, comment #2:

I've applied this patch (the first one after eight years). Please test.

Werner LEMBERG <wl>
Project Administrator
Wed 24 Jun 2009 04:30:40 PM UTC, comment #1:

Sorry, I forgot to mention the follow:

This bug is reproducible by doing the following in cygwin (copied from perforce bug report):

Make the following three files in a folder:

Jamfile:
Library TestLib : file1.c file2.c ;

file1.c:
#define FOO

file2.c:
#define BAR

Execute ftjam on that folder, execute ftjam again and they will be recompiled again rather than the expected behavior of nothing being recompiled because there was no change in this directory.

Also, I noticed the link was not formatted correctly in the original submission, copy/paste it into the address bar instead of clicking it and it should work.

Allen Farris <afarris>
Wed 24 Jun 2009 04:25:41 PM UTC, original submission:

It is the same bug that has been in perforce jam for several years. I don't expect they will every fix it but perhaps you will. The problem is that every file is recompiled in a directory even if they have not changed since the last compile. The fix is rather simple (the change he submitted works).

Link to fix:
http://public.perforce.com:8080/@md=d&cd=//guest/lawrence_you/public/jam/src/&ra=s&po=h&c=YLQ@/4382?ac=10

Allen Farris <afarris>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by wl (Posted a comment)
  • -email is unavailable- added by afarris (Submitted the item)
  • -email is unavailable- added by afarris
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-06-25 wl StatusFixed => Confirmed
        Assigned towl => freetype
        Open/ClosedClosed => Open
    2009-06-25 wl StatusNone => Fixed
        Assigned toNone => wl
        Open/ClosedOpen => Closed
    2009-06-24 afarris Carbon-Copy- => Added afarris

    Back to the top


    Powered by Savane 3.3