From owner-freebsd-ports@FreeBSD.ORG Thu Aug 30 06:49:18 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02E7216A469 for ; Thu, 30 Aug 2007 06:49:18 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.184]) by mx1.freebsd.org (Postfix) with ESMTP id 7E9C313C48A for ; Thu, 30 Aug 2007 06:49:17 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so457422mue for ; Wed, 29 Aug 2007 23:48:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NbhweEfuPqWsbZIUItPPm6PPG9yviWauvoi+8pB8vP5z8Lrv9Tqsss2Q4HLAqOKyJ5o8cxkIkSSOpErtAEGSF3n/2utHamtvPWIIp5D3MQPg9ZOBs6kJtrBGqm1Q8zHzutIaR7wkQGjpA+H/cATqnfauXLa7UR1TQhuEXJ/vyB8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=jRpVWEFmlJGIrqgEaRBd/ynbqCJjU4dRASeqPDtVIocG6FCVdiZ7kFnd21JvTUzLNSunE1De99FCC1G7qKG0GkBKt0F40nqcqIXDBv0teSt40k6eNRLANWZS03REuCk3RNK9f6f5atm04OSx/3r80NCD+GGbEVlK+TFExLLiOSQ= Received: by 10.86.54.3 with SMTP id c3mr178011fga.1188456534161; Wed, 29 Aug 2007 23:48:54 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id k29sm330093fkk.2007.08.29.23.48.53 (version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 23:48:53 -0700 (PDT) Message-ID: <46D6684E.2020409@gmail.com> Date: Thu, 30 Aug 2007 10:48:46 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Xin LI References: <46C55191.2050205@gmail.com> <20070821145603.L50579@fledge.watson.org> <46CAF217.7040204@gmail.com> <20070821151108.Y53914@fledge.watson.org> <46CAF4E9.2030700@gmail.com> <20070821152327.R53914@fledge.watson.org> <46CBE096.90805@gmail.com> <20070828175313.B90180@fledge.watson.org> <46D517FE.8050806@gmail.com> <46D51B4F.5090207@delphij.net> <46D520F0.7070708@gmail.com> <46D52333.3040109@delphij.net> <46D52799.4080105@gmail.com> <46D52A52.3010308@delphij.net> <46D54656.3030907@gmail.com> <46D59971.1030505@delphij.net> In-Reply-To: <46D59971.1030505@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: d@delphij.net, freebsd-ports@freebsd.org Subject: Re: NetXMS waiting to commit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2007 06:49:18 -0000 Xin LI wrote: > Hi, Sam, > > sam wrote: >>> I think you may want to try to build it on a -CURRENT box or with GCC >>> 4.2.x, this is not a configure problem I think. >>> >>> Let me know if you still want the config.log. >>> >>> Cheers, >>> >> i am tested netxms-port on 6.2-RELEASE i386/amd64 (without problem) > > Please understand that we really wanted it to be gcc 4.2 compatible, > because it's the version that we will ship with 7.0-RELEASE, which > will be released later this year. If it won't work with gcc 4.2 then > it would be advisable to mark it as USE_GCC=34 or so. > > My own experience is that gcc warnings indicates some real problems > (sometimes trivial or even false positive, but sometimes they can > really cause problems). > > I think NetXMS is an amazing software and we want to have it, and it > would be even better if we can ship an package that can be easily > installed with 7.0-R :-) What's the timeframe the upstream developers > will support gcc 4.2? We can fix the problems our own, but if the > upstream developers are willing to make some modifications we could > avoid some duplicated work. > > Cheers, > developer's comment: Work on making NetXMS GCC 4.2.x compatible is almost done, and next version should compile without problems. We expect to release a new version in a week or two.