Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Sep 2003 11:05:26 -0700
From:      Erin Fortenberry <efortenb@sdccd.cc.ca.us>
To:        "'freebsd-ports@freebsd.org'" <freebsd-ports@freebsd.org>
Subject:   Openssh-portable compile problems.
Message-ID:  <BBDEEDD2EB67D311A0240008C74B934595D047@ntxmidcity.sdccd.cc.ca.us>

next in thread | raw e-mail | index | archive | help
This is on 4.8R with the port changes from today via cvsup for
openssh-portable-3.6.1p2_1.

I am getting:

---------------------------------------------------------------


cc -O -pipe  -Wall -Wpointer-arith -Wno-uninitialized -I. -I.. -I. -I./..
-I/usr/local/include  -DHAVE_CONFIG_H -c bsd-arc4random.c
In file included from ../includes.h:122,
                 from bsd-arc4random.c:25:
/usr/include/sys/bitypes.h:25: conflicting types for `int8_t'
/usr/include/sys/inttypes.h:11: previous declaration of `int8_t'
/usr/include/sys/bitypes.h:26: redefinition of `u_int8_t'
/usr/include/sys/types.h:60: `u_int8_t' previously declared here
/usr/include/sys/bitypes.h:27: redefinition of `int16_t'
/usr/include/sys/inttypes.h:12: `int16_t' previously declared here
/usr/include/sys/bitypes.h:28: redefinition of `u_int16_t'
/usr/include/sys/types.h:61: `u_int16_t' previously declared here
/usr/include/sys/bitypes.h:29: redefinition of `int32_t'
/usr/include/sys/inttypes.h:13: `int32_t' previously declared here
/usr/include/sys/bitypes.h:30: redefinition of `u_int32_t'
/usr/include/sys/types.h:62: `u_int32_t' previously declared here
In file included from ../includes.h:166,
                 from bsd-arc4random.c:25:
../defines.h:194: redefinition of `int64_t'
/usr/include/sys/inttypes.h:14: `int64_t' previously declared here
*** Error code 1

Stop in
/usr/ports/security/openssh-portable/work/openssh-3.6.1p2/openbsd-compat.
*** Error code 1

Stop in /usr/ports/security/openssh-portable/work/openssh-3.6.1p2.
*** Error code 1

Stop in /usr/ports/security/openssh-portable.

---------------------------------------------------------------

I was wondering if anyone else was having this problem and if any one knew
of a fix for it.

Thanks,

Erin



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