[ECOS] OpenSSL failing to generate library

[ECOS] OpenSSL failing to generate library

[Laurie Gellatly]

Hi All,
I'm using ARM on a phytec 2294 board.
I have a working library and wanted to add openSSL to it.
Retrieved the 'epk' and loaded it via the admin tool into my current ecc. No
problem.
Deleted the entire build tree and then saved the new ecc.
When I tried to build the library an error message was generated complaining
that
.../src/crypto/bio/b_print.c error conflicting types for 'round'.

I went back and loaded a clean 'net' package for the board and only added
openSSL - same outcome.

For the moment, I've renamed 'round' in b_print.c to 'roundl' and modified
the single reference.
Anyone else had this problem? Could not see any mention of any issues with
openSSL in the archives.

Thanks 			...Laurie:{)


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] OpenSSL failing to generate library

[Andrew Lunn]

> When I tried to build the library an error message was generated complaining
> that
> .../src/crypto/bio/b_print.c error conflicting types for 'round'.


I've not seen this before. Does gcc tell you where the other
definition is?

           Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] OpenSSL failing to generate library

[Laurie Gellatly]

Can't find a definition anywhere (there is a round in vfnprintf.cxx).
Unfortunately, gcc does not say where the definition is either.
Got any other ideas?

Thanks both.                 ...Laurie:{)


-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Monday, 14 August 2006 5:12 PM
To: Laurie Gellatly
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] OpenSSL failing to generate library


> When I tried to build the library an error message was generated
complaining
> that
> .../src/crypto/bio/b_print.c error conflicting types for 'round'.


I've not seen this before. Does gcc tell you where the other
definition is?

           Andrew


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] OpenSSL failing to generate library

[Andrew Lunn]

On Mon, Aug 14, 2006 at 10:03:28AM +1000, Laurie Gellatly wrote:
> 
> 
> Hi All,
> I'm using ARM on a phytec 2294 board.
> I have a working library and wanted to add openSSL to it.
> Retrieved the 'epk' and loaded it via the admin tool into my current ecc. No
> problem.
> Deleted the entire build tree and then saved the new ecc.
> When I tried to build the library an error message was generated complaining
> that
> .../src/crypto/bio/b_print.c error conflicting types for 'round'.
> 
> I went back and loaded a clean 'net' package for the board and only added
> openSSL - same outcome.
> 
> For the moment, I've renamed 'round' in b_print.c to 'roundl' and modified
> the single reference.
> Anyone else had this problem? Could not see any mention of any issues with
> openSSL in the archives.

I took a look at this. I get a slightly different output:

/home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_print.c:562: warning: conflicting types for built-in function 'pow10'
/home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_print.c:573: warning: conflicting types for built-in function 'round'

This is with the synth target, gcc version 4.1.2.

The warning is more clear. gcc has its own round function, which is
probably double round(double x), where as the local version is 
long round(long double).

Your fix is O.K.

FYI:

The latest version of openssl, from www.openssl.org, renames this
function roundv().

         Andrew


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] OpenSSL failing to generate library

[Laurie Gellatly]

Hi Andrew,
Thanks for the confirmation. I might rename it to 'roundv' then.

BTW, should I be looking to upgrade to the latest version?
If so, how would you recommend I do that?

Thanks			...Laurie:{)


-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Andrew Lunn
Sent: Tuesday, 15 August 2006 5:57 AM
To: Laurie Gellatly
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] OpenSSL failing to generate library


On Mon, Aug 14, 2006 at 10:03:28AM +1000, Laurie Gellatly wrote:
>
>
> Hi All,
> I'm using ARM on a phytec 2294 board.
> I have a working library and wanted to add openSSL to it.
> Retrieved the 'epk' and loaded it via the admin tool into my current ecc.
No
> problem.
> Deleted the entire build tree and then saved the new ecc.
> When I tried to build the library an error message was generated
complaining
> that
> .../src/crypto/bio/b_print.c error conflicting types for 'round'.
>
> I went back and loaded a clean 'net' package for the board and only added
> openSSL - same outcome.
>
> For the moment, I've renamed 'round' in b_print.c to 'roundl' and modified
> the single reference.
> Anyone else had this problem? Could not see any mention of any issues with
> openSSL in the archives.

I took a look at this. I get a slightly different output:

/home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_
print.c:562: warning: conflicting types for built-in function 'pow10'
/home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_
print.c:573: warning: conflicting types for built-in function 'round'

This is with the synth target, gcc version 4.1.2.

The warning is more clear. gcc has its own round function, which is
probably double round(double x), where as the local version is
long round(long double).

Your fix is O.K.

FYI:

The latest version of openssl, from www.openssl.org, renames this
function roundv().

         Andrew


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] OpenSSL failing to generate library

[Gary Thomas]

Laurie Gellatly wrote:
> Hi Andrew,
> Thanks for the confirmation. I might rename it to 'roundv' then.

Isn't round() more or less the same in both realms?  If so, I would
think that the best thing would be to either remove the definition
in the OpenSSL package or make the prototypes/functions match.

> BTW, should I be looking to upgrade to the latest version?

Of what?  OpenSSL or eCos?

> If so, how would you recommend I do that?
> 
> Thanks			...Laurie:{)
> 
> 
> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org
> [mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Andrew Lunn
> Sent: Tuesday, 15 August 2006 5:57 AM
> To: Laurie Gellatly
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] OpenSSL failing to generate library
> 
> 
> On Mon, Aug 14, 2006 at 10:03:28AM +1000, Laurie Gellatly wrote:
>>
>> Hi All,
>> I'm using ARM on a phytec 2294 board.
>> I have a working library and wanted to add openSSL to it.
>> Retrieved the 'epk' and loaded it via the admin tool into my current ecc.
> No
>> problem.
>> Deleted the entire build tree and then saved the new ecc.
>> When I tried to build the library an error message was generated
> complaining
>> that
>> .../src/crypto/bio/b_print.c error conflicting types for 'round'.
>>
>> I went back and loaded a clean 'net' package for the board and only added
>> openSSL - same outcome.
>>
>> For the moment, I've renamed 'round' in b_print.c to 'roundl' and modified
>> the single reference.
>> Anyone else had this problem? Could not see any mention of any issues with
>> openSSL in the archives.
> 
> I took a look at this. I get a slightly different output:
> 
> /home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_
> print.c:562: warning: conflicting types for built-in function 'pow10'
> /home/lunn/eCos/anoncvs-clean/packages/net/openssl/current/src/crypto/bio/b_
> print.c:573: warning: conflicting types for built-in function 'round'
> 
> This is with the synth target, gcc version 4.1.2.
> 
> The warning is more clear. gcc has its own round function, which is
> probably double round(double x), where as the local version is
> long round(long double).
> 
> Your fix is O.K.
> 
> FYI:
> 
> The latest version of openssl, from www.openssl.org, renames this
> function roundv().
> 
>          Andrew
> 
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] OpenSSL failing to generate library

[Andrew Lunn]

On Mon, Aug 14, 2006 at 04:42:09PM -0600, Gary Thomas wrote:
> Laurie Gellatly wrote:
> >Hi Andrew,
> >Thanks for the confirmation. I might rename it to 'roundv' then.
> 
> Isn't round() more or less the same in both realms?

No. math.h uses double. The openssl version is for long's. That is why
i think they renamed it in newer versions of openssl.

  Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] OpenSSL failing to generate library

[Andrew Lunn]

On Tue, Aug 15, 2006 at 07:53:53AM +1000, Laurie Gellatly wrote:
> BTW, should I be looking to upgrade to the latest version?
> If so, how would you recommend I do that?

My port is quite old. The version it is based on is known to have
vunerabilities which are fixed in later versions. However, it is not a
10 minute job to upgrade the port.

If you want to port a newer version i would recommend you keep the
same style of CDL. Many of the crypto and hashing algorithms are
patented, so it is importent users have the option of not compiling
algorithms they don't want to license or use without a license. To
make this work i had the clean up the #ifdef's a little. Hopefully the
newer versions have these changes anyway. I also had to move the test
cases around, and some would just not compile, or needed access to a
filessystem which is not easy to arrange in a testcase. So i dropped
those.

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] OpenSSL failing to generate library

[Laurie Gellatly]

Thanks Andrew,
(Gary: I was asking about the upgrade to openSSL).
I see the comments in the package about the license restrictions.
I think that for my needs (email AUTH coding) none of the licensed ones are
required.

Thanks again for your help.			...Laurie:{)

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Andrew Lunn
Sent: Tuesday, 15 August 2006 8:54 AM
To: Laurie Gellatly
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] OpenSSL failing to generate library


On Tue, Aug 15, 2006 at 07:53:53AM +1000, Laurie Gellatly wrote:
> BTW, should I be looking to upgrade to the latest version?
> If so, how would you recommend I do that?

My port is quite old. The version it is based on is known to have
vunerabilities which are fixed in later versions. However, it is not a
10 minute job to upgrade the port.

If you want to port a newer version i would recommend you keep the
same style of CDL. Many of the crypto and hashing algorithms are
patented, so it is importent users have the option of not compiling
algorithms they don't want to license or use without a license. To
make this work i had the clean up the #ifdef's a little. Hopefully the
newer versions have these changes anyway. I also had to move the test
cases around, and some would just not compile, or needed access to a
filessystem which is not easy to arrange in a testcase. So i dropped
those.

        Andrew

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

RE: [ECOS] OpenSSL failing to generate library

[Sinan KAYA]

Gcc tells this only if you have some prototype in a header file and it's
included in your source code.
Sinan.
 

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Monday, August 14, 2006 10:12 AM
To: Laurie Gellatly
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] OpenSSL failing to generate library

> When I tried to build the library an error message was generated
complaining
> that
> .../src/crypto/bio/b_print.c error conflicting types for 'round'.


I've not seen this before. Does gcc tell you where the other
definition is?

           Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss