Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 May 2004 21:37:57 +0200
From:      Tijl Coosemans <tijl@ulyssis.org>
To:        sparc64@freebsd.org
Subject:   Re: [ports-sparc64@bento.FreeBSD.org: libticables-3.7.7_2 failed on sparc64 5]
Message-ID:  <20040511213757.37a2189e.tijl@ulyssis.org>
In-Reply-To: <20040511010823.GB72214@xor.obsecurity.org>
References:  <20040511010823.GB72214@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 May 2004 18:08:23 -0700, Kris Kennaway wrote:

> ----- Forwarded message from User Ports-sparc64
> <ports-sparc64@bento.FreeBSD.org> -----

Full build log at
http://bento.freebsd.org/errorlogs/sparc64-5-latest/libticables-3.7.7_2.log

> In file included from ioports.c:45:
> /usr/include/machine/sysarch.h:53: error: syntax error before
> "utrap_entry_t"
> /usr/include/machine/sysarch.h:64: error: syntax error before "type"
> gmake[2]: *** [ioports.lo] Error 1
> gmake[2]: Leaving directory
> `/tmp/a/ports/comms/libticables/work/libticables-3.7.7/src'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory
> `/tmp/a/ports/comms/libticables/work/libticables-3.7.7'
> gmake: *** [all] Error 2
> *** Error code 2

Apparently src/sys/sparc64/include/sysarch.h uses
utrap_entry_t and utrap_handler_t without defining them. They are
however defined in src/sys/sparc64/utrap.h.

So I'm wondering, should I file a PR for my port to include
machine/utrap.h(?) before machine/sysarch.h in case
of a sparc64 build (or get rid of it since it is only used on i386),
or is this a bug and should src/sys/sparc64/include/sysarch.h include
machine/utrap.h (probably wrapped inside an #ifndef _KERNEL)?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040511213757.37a2189e.tijl>