From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SZmWe-0000Iv-G2 for openembedded-core@lists.openembedded.org; Wed, 30 May 2012 19:17:38 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q4UH7Iow023694; Wed, 30 May 2012 18:07:18 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23393-04; Wed, 30 May 2012 18:07:14 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q4UH79cU023688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 May 2012 18:07:10 +0100 Message-ID: <1338397629.20169.169.camel@ted> From: Richard Purdie To: Enrico Scholz Date: Wed, 30 May 2012 18:07:09 +0100 In-Reply-To: References: <1338391023-31189-1-git-send-email-enrico.scholz@sigma-chemnitz.de> <1338392680.20169.148.camel@ted> <1338396454.20169.163.camel@ted> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: Patches and discussions about the oe-core layer Subject: Re: [PATCH] libtasn: fixed cross build issue X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2012 17:17:38 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-05-30 at 18:54 +0200, Enrico Scholz wrote: > Richard Purdie writes: > > >> setting HELP2MAN environment to 'true' for cross-builds might be a > >> general solution.... But this does not seem to be implemented... > > > > Right, I remember looking into this and its hard to disable. I've pushed > > a PATH change to address this problem... > > But this makes 'help2man' completely unavailable which might break > man-page generation for -native (where 'help2man' works) or for every > package which requires a working 'help2man' tool. help2man is *totally* useless in any cross situation. We also don't need/want man-pages for native tools so I can't see a case where this is a problem... Cheers, Richard