From: Gilles E. <g....@fr...> - 2010-09-26 15:03:01
|
----- Original Message ----- From: <ow...@us...> To: <ipc...@li...> Sent: Sunday, September 26, 2010 4:14 PM Subject: [Ipcop-svn] SF.net SVN: ipcop:[4973] ipcop/trunk/lfs/lsof > Revision: 4973 > http://ipcop.svn.sourceforge.net/ipcop/?rev=4973&view=rev > Author: owes > Date: 2010-09-26 14:14:32 +0000 (Sun, 26 Sep 2010) > > Log Message: > ----------- > lsof -v outputs compiler flags, including kernelversion. Include lsof in update after kernelupgrade using new datestamp. > > Modified Paths: > -------------- > ipcop/trunk/lfs/lsof > > Modified: ipcop/trunk/lfs/lsof > =================================================================== > --- ipcop/trunk/lfs/lsof 2010-09-26 13:10:15 UTC (rev 4972) > +++ ipcop/trunk/lfs/lsof 2010-09-26 14:14:32 UTC (rev 4973) > @@ -45,7 +45,7 @@ > > # Used to include same timestamp for all > # This is the release date > -DATESTAMP = "2010-07-29 12:09:00" > +DATESTAMP = "2010-09-21 20:08:35" > I don't think that's the better answer. If we upgrade to gcc-4.4.5, should we update the timestamp again? Instead, should we not add lsof in files-with-different-md5 with the multiples reasons? By the way, I have compiled gcc-4.4.5-RC-20100924. I still need to check which files have changed. gcc-4.4.5 should be released at the end of next week. Gilles |