unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin <parozusa@web.de>
To: emacs-devel@gnu.org
Subject: Re: https://sourceforge.net/projects/emacs-bin/files/snapshots/
Date: Mon, 31 Mar 2014 20:50:47 +0200	[thread overview]
Message-ID: <82ob0m19tk.fsf@web.de> (raw)
In-Reply-To: CAH8Pv0h=-1264Z3Bh1+5uHM03Q5b+edMbm5PZdBQRCTpabiVMA@mail.gmail.com


Dani Moncayo writes:

> On Mon, Mar 31, 2014 at 10:58 AM, Martin <parozusa@web.de> wrote:
>>
>>   emacs-r116766-20140315-w32-bin.7z
>>
>> compiled with libxml2 support,
>>
>>   emacs-24-20140330112454-w32-bin.7z
>>   emacs-trunk-20140329120847-w32-bin.7z
>>
>> not.
>>
>> Correct ?
>
> I've just checked the log files for these 3 builds, and in all of them
> I see a successful check for libxml-2.0:
>
>   checking for libxml-2.0 > 2.6.17... yes
> CFLAGS='-Ic:/mingw/include/libxml2  ' LIBS='-Lc:/mingw/lib -lxml2  '
>
>
> So, I'd say that the 3 binaries above were successfully compiled with
> libxml2 support.

Hi Dani,

thank you for response. My test case:

I have placed the same libxml2 dll in every emcas bin directory.

  c:\cygwin\bin\find.exe . "(" -iname 'libxml2*.dll' -type f ")" -exec c:\cygwin\bin\ls -ld {} ";"
  -rwxrwxrwx+   1 plus None  4470354 Nov 29 11:47 emacs-pretest/bin/libxml2-2.dll
  -rwxrwxrwx+   1 plus None  4470354 Nov 29 11:47 emacs-trunk/bin/libxml2-2.dll
  -rwxrwxrwx+   1 plus None  4470354 Nov 29 11:47 emacs-trunk-2014-03-31-09-52-01/bin/libxml2-2.dll

Gnus v5.13

When I open the same email from my IMAP account (arcor.de, may be
followed up to you by private mail), it ist diplayed correctly with

  GNU Emacs 24.3.50.1 (i686-pc-mingw32) of 2014-03-15 on LEG570  (emacs-trunk)                         

with                                 

  GNU Emacs 24.3.50.1 (i686-pc-mingw32) of 2014-03-30 on LEG570  (emacs-pretest)                       
  GNU Emacs 24.4.50.1 (i686-pc-mingw32) of 2014-03-30 on LEG570  (emacs-trunk-2014-03-31-09-52-01)

I get the message "libxml2 library not found" and an empty mail body.

Martin




  reply	other threads:[~2014-03-31 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  8:58 https://sourceforge.net/projects/emacs-bin/files/snapshots/ Martin
2014-03-31  9:09 ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Dani Moncayo
2014-03-31  9:11   ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Dani Moncayo
2014-03-31 17:30 ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Dani Moncayo
2014-03-31 18:50   ` Martin [this message]
2014-03-31 19:15     ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Eli Zaretskii
2014-03-31 19:19       ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Eli Zaretskii
2014-03-31 19:36         ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Dani Moncayo
2014-04-01 19:01       ` https://sourceforge.net/projects/emacs-bin/files/snapshots/ Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=82ob0m19tk.fsf@web.de \
    --to=parozusa@web.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).