Date: Thu, 14 Nov 2002 17:10:30 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Kris Kennaway <kris@obsecurity.org>, suken woo <wsk@ns.gddsn.org.cn>, freebsd-current <freebsd-current@FreeBSD.ORG> Subject: Re: after cvsup make chinpui3 get undefined reference error Message-ID: <20021115011030.GB12616@rot13.obsecurity.org> In-Reply-To: <20021114233659.GA45770@troutmask.apl.washington.edu> References: <3DD2EEEF.3060106@mail.gddsn.org.cn> <20021114230051.GA12183@rot13.obsecurity.org> <20021114233659.GA45770@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 14, 2002 at 03:36:59PM -0800, Steve Kargl wrote: > On Thu, Nov 14, 2002 at 03:00:51PM -0800, Kris Kennaway wrote: > > On Thu, Nov 14, 2002 at 08:31:43AM +0800, suken woo wrote: > > > g++ -o chinput chinput.o init.o server.o config.o color.o util.o=20 > > > convert.o IC.o XIM.o focus.o root.o overspot.o onspot.o offspot.o=20 > > > voice.o keyboard.o handw.o hwengine.o loop.o -L/usr/X11R6/lib -lXext= =20 > > > -lX11 ./IMdkit/lib/libXimd.a -L../../unicon-im/client=20 > > > -L../../unicon-im/server -limmclient=20 > > > -Wl,-rpath=3D/usr/local/lib/Chinput/im -limm_server -lc_r -lc -lImlib > > > ../../unicon-im/server/libimm_server.so: undefined reference to=20 > > > `ostream::operator<<(char const*)' > > > ../../unicon-im/server/libimm_server.so: undefined reference to `cout' > > > *** Error code 1 > >=20 > > Again, it's unfortunate but expected that many ports fail to build on > > -current. There's not much point in reporting them (they're all > > listed at http://bento.freebsd.org) unless you can supply a patch to > > fix it. > >=20 >=20 > I just had 3 PR (44290,44291,45201) closed because no one > would commit the patches to fix the builds on -current. So the PR was closed with the problems still existing? That shouldn't have happened. > Two of these PRs were submitted almost a month ago. So, > supplying patch hardly guarantees the port will be fixed. Well, there are never guarantees in this game, but there's certainly a greater chance. I've done a number of passes through the PR database committing PRs that fix build errors, and we have 3 new committers recently who are also working on this. Kris --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE91EmGWry0BWjoQKURAqBLAKDNf2j1u/nnPOE6vfl1JwbpCOxqUwCg78Gw Sb8cYYQH7e/9O1mye57YrPY= =Gv2K -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021115011030.GB12616>