headers
Gerfried Fuchs | 20 Jul 2005 13:17
X-Face
Picon

libetpan 0.38 released

        Hi!

 ... and eventually a new release happens. I haven't announced 0.37 to
this list because I was in HEL[1] and Hoa told me not too much later
that there needs to be a bugfix release anyway.

 So here it is! All new! All hot! Just release! And, erm... including
the mentioned bugfix related to SSL. IMAP handling was improved too, and
yes, there really is something new! SASL! If you need it, it's there
now.

 Like always, feel free to bother us with bug reports, and have a nice
time.

 So long,
Alfie
[1] <http://debconf.org/debconf5/>
--

-- 
tar: Cowardly refusing to create an empty archive
Permalink | Reply | 0 comments |
headers
Alex S Moore | 23 Jul 2005 19:06

Build on Solaris

I am trying to build libetpan 0.38 on Solaris 8 using Sun's compiler. 
However, I am getting the following error and do not know how to fix it. 
  Can someone create a patch to fix this?

---
  cc -c -I../../include -I../.. -I. -fast -xarch=v8 
-I/opt/csw/bdb4/include -I/opt/csw/include -D_REENTRANT -DHAVE_CONFIG_H 
mailstream.c  -KPIC -DPIC -o .libs/mailstream.o
"mailstream.c", line 402: syntax error before or at: .
cc: acomp failed for mailstream.c
*** Error code 1
make: Fatal error: Command failed for target `mailstream.lo'
Current working directory 
/export/medusa/asmoore/build/libetpan-0.38/src/data-types
*** Error code 1
---

Thanks, Alex

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Permalink | Reply | 4 comments |
headers
DINH Viet Hoa | 23 Jul 2005 19:26
Picon
Favicon

Re: Build on Solaris

On 23 Jul 2005, at 19:06, Alex S Moore wrote:

> I am trying to build libetpan 0.38 on Solaris 8 using Sun's  
> compiler. However, I am getting the following error and do not know  
> how to fix it.  Can someone create a patch to fix this?
>
> ---
>  cc -c -I../../include -I../.. -I. -fast -xarch=v8 -I/opt/csw/bdb4/ 
> include -I/opt/csw/include -D_REENTRANT -DHAVE_CONFIG_H  
> mailstream.c  -KPIC -DPIC -o .libs/mailstream.o
> "mailstream.c", line 402: syntax error before or at: .
> cc: acomp failed for mailstream.c
> *** Error code 1
> make: Fatal error: Command failed for target `mailstream.lo'
> Current working directory /export/medusa/asmoore/build/ 
> libetpan-0.38/src/data-types
> *** Error code 1
> ---

You will see much problems like this. They will be surrounded by such  
defines.

#ifdef _MSC_VER
#else
#endif

Just replace "#ifdef _MSC_VER" with "#if 1".

You may try to use gcc to compile.
However, I'll try to find write some fix for Sun Compiler.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Alex S Moore | 23 Jul 2005 19:40

Re: Build on Solaris

DINH Viet Hoa wrote:
> Just replace "#ifdef _MSC_VER" with "#if 1".
> 
> You may try to use gcc to compile.
> However, I'll try to find write some fix for Sun Compiler.
> 
> Whenever there is constant structures defined this way, you may use  
> _MSC_VER alternative.
> And tell about the result.
> 
Thanks for this.  I will give this a try.

Since I am  building libetpan for use with sylpheed-claws, which uses 
Sun's compiler, I prefer to use Sun's compiler with libetpan.  It 
probably does not really matter:>

Thanks, Alex

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Permalink | Reply | 0 comments |
headers
Alex S Moore | 26 Jul 2005 02:24

Re: Build on Solaris

DINH Viet Hoa wrote:
> On 23 Jul 2005, at 19:06, Alex S Moore wrote:
> 
>> ---
>>  cc -c -I../../include -I../.. -I. -fast -xarch=v8 -I/opt/csw/bdb4/ 
>> include -I/opt/csw/include -D_REENTRANT -DHAVE_CONFIG_H  mailstream.c  
>> -KPIC -DPIC -o .libs/mailstream.o
>> "mailstream.c", line 402: syntax error before or at: .
>> cc: acomp failed for mailstream.c
>> *** Error code 1
>> make: Fatal error: Command failed for target `mailstream.lo'
>> Current working directory /export/medusa/asmoore/build/ 
>> libetpan-0.38/src/data-types
>> *** Error code 1
>> ---
> 
> 
> You will see much problems like this. They will be surrounded by such  
> defines.
> 
> #ifdef _MSC_VER
> #else
> #endif
> 
> Just replace "#ifdef _MSC_VER" with "#if 1".
> 
> You may try to use gcc to compile.
> However, I'll try to find write some fix for Sun Compiler.
> 
> Whenever there is constant structures defined this way, you may use
(Continue reading)

Permalink | Reply | 1 comment |
headers
DINH Viêt Hoà | 26 Jul 2005 16:06
Picon
Favicon

Re: Build on Solaris

On 26 Jul 2005, at 02:24, Alex S Moore wrote:

> DINH Viet Hoa wrote:
>
>> On 23 Jul 2005, at 19:06, Alex S Moore wrote:
>>
>>> ---
>>>  cc -c -I../../include -I../.. -I. -fast -xarch=v8 -I/opt/csw/ 
>>> bdb4/ include -I/opt/csw/include -D_REENTRANT -DHAVE_CONFIG_H   
>>> mailstream.c  -KPIC -DPIC -o .libs/mailstream.o
>>> "mailstream.c", line 402: syntax error before or at: .
>>> cc: acomp failed for mailstream.c
>>> *** Error code 1
>>> make: Fatal error: Command failed for target `mailstream.lo'
>>> Current working directory /export/medusa/asmoore/build/  
>>> libetpan-0.38/src/data-types
>>> *** Error code 1
>>> ---
>>>
>> You will see much problems like this. They will be surrounded by  
>> such  defines.
>> #ifdef _MSC_VER
>> #else
>> #endif
>> Just replace "#ifdef _MSC_VER" with "#if 1".
>> You may try to use gcc to compile.
>> However, I'll try to find write some fix for Sun Compiler.
>> Whenever there is constant structures defined this way, you may  
>> use  _MSC_VER alternative.
>> And tell about the result.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alex S Moore | 27 Jul 2005 03:27

no setenv/unsetenv on Solaris

Since there is no setenv or unsetenv on Solaris, I made a patch which 
may work ok.  Please see attached.

Functionally, I think that the Solaris function putenv with no value 
assigned to the environment variable will leave the variable without a 
value in the environment list.  Not sure about that, but if it is true, 
does that work for libetpan?

I used my previous defines for __SUNPRO_CC, since if someone is using 
that compiler, they are probably on Solaris.  This may not be the best 
way, but I do not know how to add code to configure to determine if the 
setenv and unsetenv or putenv functions are available.  Maybe a 
HAVE_SETENV defines?  Could someone do this?  I am having the same 
problem with sylpheed-claws, so I will see what the claws developers 
recommend.

I am not a C programmer by trade, so please check my code carefully to 
make sure that it passes security protocols, etc.

Would you add this logic, or your revision, to the base source?

Thanks, Alex
Attachment (patch-mailstorage_tools.diff): text/x-patch, 1381 bytes
Permalink | Reply | 1 comment |
headers
DINH Viêt Hoà | 27 Jul 2005 11:37
Picon
Favicon

Re: no setenv/unsetenv on Solaris

On 27 Jul 2005, at 03:27, Alex S Moore wrote:

> Since there is no setenv or unsetenv on Solaris, I made a patch  
> which may work ok.  Please see attached.
>
> Functionally, I think that the Solaris function putenv with no  
> value assigned to the environment variable will leave the variable  
> without a value in the environment list.  Not sure about that, but  
> if it is true, does that work for libetpan?
>
> I used my previous defines for __SUNPRO_CC, since if someone is  
> using that compiler, they are probably on Solaris.  This may not be  
> the best way, but I do not know how to add code to configure to  
> determine if the setenv and unsetenv or putenv functions are  
> available.  Maybe a HAVE_SETENV defines?  Could someone do this?  I  
> am having the same problem with sylpheed-claws, so I will see what  
> the claws developers recommend.
>
> I am not a C programmer by trade, so please check my code carefully  
> to make sure that it passes security protocols, etc.
>
> Would you add this logic, or your revision, to the base source?

This will be scheduled for commit (I will avoid use of strlcat()  
since this is does not conform to POSIX).

--

-- 
DINH Viet Hoa

-------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |

Gmane