Mail #14352 (Unformatted/full headers)

Back to main page of archive

Previous mail   Next mail   Formatted
Overview  10 days   Subject   Date   Thread   Author  

From gpc-owner+M7999@gnu.de Thu Jun 12 17:25:12 2008
Received: from localhost ([127.0.0.1] helo=gnu.de)
	by ngc224.gerwinski.de with smtp (Exim 4.50 #1 (Debian))
	id 1K6oVr-0005E2-BY; Thu, 12 Jun 2008 17:14:55 +0200
Received: from hu-out-0506.google.com ([72.14.214.233])
	by ngc224.gerwinski.de with esmtp (Exim 4.50 #1 (Debian))
	id 1K6oVA-00058b-FZ
	for <gpc@gnu.de>; Thu, 12 Jun 2008 17:14:47 +0200
Received: by hu-out-0506.google.com with SMTP id 28so4962410hub.21
        for <gpc@gnu.de>; Thu, 12 Jun 2008 08:13:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:cc:in-reply-to:mime-version:content-type:references;
        bh=1q/BAMpbHYFKRyUmSQQvvMoMBtglP/eMOYOUd6DIWNs=;
        b=Spje/tWr2INGcEBT4VCri2/tCgbwEgl8h65nE20SyWNregvKNqtlAT0EgCiJKwptjt
         xNkHXnzYpI7RWfviOCp6S+Ce66ZtWYMiV3Nx5+TEixKCT1d5x6GY5LI1JXugrqkH629H
         01II3dC8UEkHUnKpBxYGTg6FUxfPcGyQfj4D4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:references;
        b=Mh9VyH5CSv89jGiJu2l/m7LZKgrAhK3nHNNTOt8ymAk1xOsHQ8ukYAERr6+T7Zh9Dt
         iyoxorfpa+l7TE9HNNVQOtUeBZ2yXP9lppjcSrtnujz6UC+ZlSp5WP0jvvjMGI4EtGMS
         I19r7+xRxCf6Anw+J34yN8Q7RTflAAsRlf8F4=
Received: by 10.82.187.2 with SMTP id k2mr90945buf.16.1213283630273;
        Thu, 12 Jun 2008 08:13:50 -0700 (PDT)
Received: by 10.82.114.7 with HTTP; Thu, 12 Jun 2008 08:13:50 -0700 (PDT)
Message-ID: <f70d15390806120813o3497d10cx7f9887ed50b246c2@mail.gmail.com>
Date: Thu, 12 Jun 2008 09:13:50 -0600
From: "Yang Lao" <laoyanger@gmail.com>
To: "Waldek Hebisch" <hebisch@math.uni.wroc.pl>
Subject: Re: GPC and the Linux Standard Base
Cc: gpc@gnu.de
In-Reply-To: <E1K3GR2-00064F-SQ@hera.math.uni.wroc.pl>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_13008_31535474.1213283630258"
References: <f70d15390806020816k3fd35c6lb7c12c6fae0654d2@mail.gmail.com>
	 <E1K3GR2-00064F-SQ@hera.math.uni.wroc.pl>
X-Warning: 72.14.214.233 is in a black list at spam.dnsbl.sorbs.net
X-Spam-Score: -2.7 (--)
Precedence: bulk
Sender: gpc-owner@gnu.de

------=_Part_13008_31535474.1213283630258
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Mon, Jun 2, 2008 at 2:15 PM, Waldek Hebisch <hebisch@math.uni.wroc.pl>
wrote:

> Yang Lao wrote:
> > I wonder if any version of gpc for linux is compliant or conformant
> > with the Linux Standard Base. When I run your hello program through
> > their lsbappchk it gives messages like this:
> >
> > FAIL
> > Symbol isnanl is used, but is not included in LSB 3.2 (Core & C++ &
> Desktop)
> >
>
> I belive that short answer in no.  Longer answer: IIUC Linux Standard
> Base is a _binary_ specification.  "Canonical" gpc distribution
> is in source form.  In particular configure/build process is
> supposed to discover and use capabilities of the target platform.
> So one way to get LSB compliant gpc would be to compile gpc
> on "true" LSB system -- that is system which provides all LSB
> specified capabilities and nothing more.
>
> Has anyone estimated whether this is feasible?

------=_Part_13008_31535474.1213283630258
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Mon, Jun 2, 2008 at 2:15 PM, Waldek Hebisch &lt;<a href="mailto:hebisch@math.uni.wroc.pl">hebisch@math.uni.wroc.pl</a>&gt; wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Yang Lao wrote:<br>
&gt; I wonder if any version of gpc for linux is compliant or conformant<br>
&gt; with the Linux Standard Base. When I run your hello program through<br>
&gt; their lsbappchk it gives messages like this:<br>
&gt;<br>
&gt; FAIL<br>
&gt; Symbol isnanl is used, but is not included in LSB 3.2 (Core &amp; C++ &amp; Desktop)<br>
&gt;<br>
<br>
</div></div>I belive that short answer in no. &nbsp;Longer answer: IIUC Linux Standard<br>
Base is a _binary_ specification. &nbsp;&quot;Canonical&quot; gpc distribution<br>
is in source form. &nbsp;In particular configure/build process is<br>
supposed to discover and use capabilities of the target platform.<br>
So one way to get LSB compliant gpc would be to compile gpc<br>
on &quot;true&quot; LSB system -- that is system which provides all LSB<br>
specified capabilities and nothing more.<br>
<br></blockquote><div>Has anyone estimated whether this is feasible?<br><br>&nbsp;</div></div>

------=_Part_13008_31535474.1213283630258--

Previous mail   Next mail   Formatted
Overview  10 days   Subject   Date   Thread   Author  

In reply to

Back to main page of archive

Note: This page contains information that does not originate from the owner of this web site, but from the authors of the mails archived. The owner of this web site is not responsible for the content of such information. Any use of that infomation requires the consent of the respective author.

Where WWW addresses (URLs) in the mails archived are marked as hyperlinks, this is only for the comfort of the reader. The content of the web pages linked to like this does not necessarily reflect the opinion of the owner of this web site or of the authors of the mails archived. The owner of this web site is not responsible for the content of such web pages. Those pages are explicitly not to be considered as part of the content of this page, but merely as references.

This page was created by Crystal 0.999 (Linux 2.4.27/i686).