Frederik Schueler [EMAIL PROTECTED] writes:
Hello,
On Fri, Jan 28, 2005 at 05:05:44PM +0100, Jérôme Marant wrote:
The bug is open since 260 days now.
Yes, but amd64 is not an official Debian port yet (and sarge is not
released for amd64), so it has always been in the lowest priorities.
Frederik Schueler [EMAIL PROTECTED] writes:
Hello,
what is the state of the emacs21 amd64 build patch?
may I politely ask why it is still not included in the source package?
The CVS is fixed but differently from what I hacked together.
The maintainer did send a backport patch from CVS but
Hello,
what is the state of the emacs21 amd64 build patch?
may I politely ask why it is still not included in the source package?
we have at least 10 packages FTBFS because of this currently, among them
important packages like auctex and python2.3.
The bug is open since 260 days now.
Kind
Quoting Frederik Schueler [EMAIL PROTECTED]:
Hello,
what is the state of the emacs21 amd64 build patch?
may I politely ask why it is still not included in the source package?
we have at least 10 packages FTBFS because of this currently, among them
important packages like auctex and
Frederik Schueler [EMAIL PROTECTED] writes:
what is the state of the emacs21 amd64 build patch?
may I politely ask why it is still not included in the source package?
we have at least 10 packages FTBFS because of this currently, among them
important packages like auctex and python2.3.
As
Rob Browning [EMAIL PROTECTED] writes:
Jérôme: so was one of those patches good enough that I should go ahead
and apply it? (We can test on one of the ia64 machines if we need
to.)
The latest one is the good one. BTW, It requires a modification of
configure.in.
I could have applied it a
Hello,
On Fri, Jan 28, 2005 at 05:05:44PM +0100, Jérôme Marant wrote:
The bug is open since 260 days now.
Yes, but amd64 is not an official Debian port yet (and sarge is not
released for amd64), so it has always been in the lowest priorities.
Thats true. Sadly we won't support amd64 in
7 matches
Mail list logo
