Tom Tromey wrote:
> I'm unaware of a libffi port to HPPA. If there is one, it hasn't been
> integrated into the main libffi sources :-(
There is none.
AG
At (time_t)1008187389 Matthew Wilcox wrote:
> Er. Userspace should _never_ include asm/* headers.
Switching to signal.h (which pulls in bits/sigcontext.h) worked
for mips, but causes other problems on sparc:
signal.c:33: parse error before `__siginfo_t'
signal.c:33: warning: function declaratio
On Wed, Dec 12, 2001 at 12:56:53PM -0700, Tom Tromey wrote:
> I'm unaware of a libffi port to HPPA. If there is one, it hasn't been
> integrated into the main libffi sources :-(
Nobody's made libffi compile on debian/hppa yet:
$ madison libffi2
libffi2 | 1:3.0.2-4 | testing | alpha, ar
On Wed, Dec 12, 2001 at 02:34:22PM -0500, John R. Daily wrote:
> I'm cc'ing the ports in question in hopes that some of these
> problems can be solved by developers more familiar with those
> platforms. I haven't included s390, because the failure to build
> there seems to involve several missing d
> "John" == John R Daily <[EMAIL PROTECTED]> writes:
John> hppa is not supported at all; the only parisc configuration files
John> are for hpux, not linux. This may be circumventable via libffi,
John> or the existing hpux configuration files might be useful to
John> create linux ones.
I'm una
I've been doing some work to ensure kaffe's availability on the
ia64 port. 1.0.6 has yet to make it into testing, and there is
much work to be done if woody is to ship with a reasonably
up-to-date version.
I'm cc'ing the ports in question in hopes that some of these
problems can be solved by devel
Tom Tromey wrote:
> I'm unaware of a libffi port to HPPA. If there is one, it hasn't been
> integrated into the main libffi sources :-(
There is none.
AG
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
At (time_t)1008187389 Matthew Wilcox wrote:
> Er. Userspace should _never_ include asm/* headers.
Switching to signal.h (which pulls in bits/sigcontext.h) worked
for mips, but causes other problems on sparc:
signal.c:33: parse error before `__siginfo_t'
signal.c:33: warning: function declarati
On Wed, Dec 12, 2001 at 12:56:53PM -0700, Tom Tromey wrote:
> I'm unaware of a libffi port to HPPA. If there is one, it hasn't been
> integrated into the main libffi sources :-(
Nobody's made libffi compile on debian/hppa yet:
$ madison libffi2
libffi2 | 1:3.0.2-4 | testing | alpha, a
On Wed, Dec 12, 2001 at 02:34:22PM -0500, John R. Daily wrote:
> I'm cc'ing the ports in question in hopes that some of these
> problems can be solved by developers more familiar with those
> platforms. I haven't included s390, because the failure to build
> there seems to involve several missing
> "John" == John R Daily <[EMAIL PROTECTED]> writes:
John> hppa is not supported at all; the only parisc configuration files
John> are for hpux, not linux. This may be circumventable via libffi,
John> or the existing hpux configuration files might be useful to
John> create linux ones.
I'm un
I've been doing some work to ensure kaffe's availability on the
ia64 port. 1.0.6 has yet to make it into testing, and there is
much work to be done if woody is to ship with a reasonably
up-to-date version.
I'm cc'ing the ports in question in hopes that some of these
problems can be solved by deve
> LoadModule jk_module /usr/lib/apache/1.3/mod_jk.so
>
> # The following line is for apacheconfig - DO NOT REMOVE!
> JkWorkersFile /etc/tomcat/jk/workers.properties
> Include /etc/tomcat/auto/mod_jk.conf
>
this finally seems to work.
Now I can avoid using a static file :-)
ThanX
mfg Soeren
> LoadModule jk_module /usr/lib/apache/1.3/mod_jk.so
>
> # The following line is for apacheconfig - DO NOT REMOVE!
> JkWorkersFile /etc/tomcat/jk/workers.properties
> Include /etc/tomcat/auto/mod_jk.conf
>
this finally seems to work.
Now I can avoid using a static file :-)
ThanX
mfg Soeren
Ainsi parlait Kevin A. Burton :
> > > Due to the WORA nature of Java applications, a lot of projects assume
> > > they are the only package management system in existence.
> >
> > And they're right, if you take into account that a cross-platform app
> > needs a cross-platform package management sys
Ainsi parlait Kevin A. Burton :
> > > Due to the WORA nature of Java applications, a lot of projects assume
> > > they are the only package management system in existence.
> >
> > And they're right, if you take into account that a cross-platform app
> > needs a cross-platform package management sy
16 matches
Mail list logo
