--- Comment #10 from jakub at gcc dot gnu dot org 2009-01-09 14:30 ---
This is an obvious bug in fastjar-0.97:
ub4
unix2dostime (time_t *unix_time)
{
struct tm *ltime = localtime (unix_time);
int year = ltime->tm_year - 80;
...
}
int make_manifest(int jfd, const char *mf_name, int
--- Comment #9 from doko at ubuntu dot com 2009-01-09 13:32 ---
yes, fastjar is segfaulting for the test
fastjar -cf conftest.jar
seen as well, when building with current 4.1 and 4.2 branches. a fastjar built
with 3.4.6 works ok.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3
--- Comment #8 from arthur dot loiret at gmail dot com 2009-01-09 09:15
---
I can reproduce it on Debian unstable. The problem is in Debian's fastjar on
ia64:
(cd classes; \
/usr/bin/fastjar cf ../tools.zip `find . -name .svn -prune -o -type f
-print`; \
cd ..)
/bin/sh:
--- Comment #7 from doko at ubuntu dot com 2009-01-05 18:33 ---
> Can you reproduce it with vanilla trunk?
yes.
now, building with binutils 2.18 and glibc-2.7 lets the build succeed, building
with binutils-2.19 and glibc-2.9 (Ubuntu jaunty) lets the build fail. I'm
trying next to updat
--- Comment #6 from jakub at gcc dot gnu dot org 2009-01-05 11:54 ---
Can you reproduce it with vanilla trunk? I've certainly bootstrapped/regtested
the trunk on ia64-linux several times recently.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326
--- Comment #5 from doko at ubuntu dot com 2008-12-09 19:50 ---
which versions of binutils/glibc are used? for debian these are binutils-2.18.1
and glibc-2.7.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326
--- Comment #4 from steven at gcc dot gnu dot org 2008-12-09 18:53 ---
I have had no trouble bootstrapping 4.4 on ia64-unknown-linux-gnu (Debian) in
the last two weeks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38326
--- Comment #3 from ebotcazou at gcc dot gnu dot org 2008-12-09 18:32
---
Now on to this one. :-) Is 20081115 the date of the first failure? 08 was
fine?
There are test results for IA-64/Linux (suse-linux and unknown-linux) both
4.3.3
and 4.4.0 posted on the gcc-testresults on a daily