Terrence Brannon | 2 Oct 02:45 2008
Picon

Warning: .stabs: description field '10543' too big, try a different debug format


Hello, I am using Cygwin and attempting to compile lxml. It worked under Cygwin
on one laptop, so I dont know what is going on here --- both Cygwin distros are
up to date.

I am using Stackless Python if that makes a difference.

Administrator <at> LIFEBOOK /usr/local/bin : $NAGARE_BIN/easy_install 'nagare[full]'
Searching for nagare[full]
Best match: nagare 0.1.0
Processing nagare-0.1.0-py2.5.egg
nagare 0.1.0 is already the active version in easy-install.pth
Installing nagare-admin script to /home/Administrator/prg/nagare-home/bin

Using
/home/Administrator/prg/nagare-home/lib/python2.5/site-packages/nagare-0.1.0-py2.5.egg
Processing dependencies for nagare[full]
Searching for lxml==2.1.1
Reading http://www.nagare.org/download/
Reading http://pypi.python.org/simple/lxml/
Reading http://codespeak.net/lxml
Best match: lxml 2.1.1
Downloading http://codespeak.net/lxml/lxml-2.1.1.tgz
Processing lxml-2.1.1.tgz
Running lxml-2.1.1/setup.py -q bdist_egg --dist-dir
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/easy_install-yy5d-E/lxml-2.1.1/egg-dist-tmp-gaRX38
Building lxml version 2.1.1.
NOTE: Trying to build without Cython, pre-generated 'src/lxml/lxml.etree.c'
needs to be available.
Using build configuration of libxslt 1.1.24
Building against libxml2/libxslt in the following directory: /usr/lib
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s: Assembler messages:
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22618: Warning: .stabs:
description field '10543' too big, try a different debug format
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22619: Warning: .stabs:
description field '10543' too big, try a different debug format
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22620: Warning: .stabs:
description field '10543' too big, try a different debug format
/cygdrive/c/DOCUME~1/ADMINI~1/LOCALS~1/Temp/ccULuerS.s:22621: Warning: .stabs:
description field '10543' too big, try a different debug format
_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
jholg | 2 Oct 08:49 2008
Picon
Picon

Re: Warning: .stabs: description field '10543' too big, try a different debug format

Hi,


I've no experience whatsoever with cygwin, but 


Using build configuration of libxslt 1.1.24
Building against libxml2/libxslt in the following directory: /usr/lib

Have you compared the libxml2/libxslt build configurations of the successful/unsuccessful

build systems?

 

lxml takes configuration from libxml2/libxslt.

 

You can verify these by looking into xslt-config or by running it with its several options, e.g.

 

$ xslt-config --cflags
-I/apps/prod//include -I/apps/prod//include/libxml2

 

 

So maybe certain offending debug flags are set on one system?

 

Holger 




--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf <at> gmx
_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
Hanni Ali | 2 Oct 15:56 2008
Picon

Compilation of lxml on Windows 64-bit

Hi All,

Came across this little gem of a Python module which seems able to translate some XML reports for me nicely.

I was very pleased to see a Python 2.6 installer for windows, made checking it out much easier than many modules I use. So thanks for that.

However although my testing seems to confirm this is the ideal module I do need to deploy to our production environment which is a 64-bit Windows environment running Python 2.6 (I code on  32-bit box for simplicity/resource reasons).

Has anyone compiled and used lxml on this platform combination? If not does anyone foresee me having any issues compiling it for this platform?

Thanks,

Hanni
_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
Sidnei da Silva | 2 Oct 16:06 2008

Re: Compilation of lxml on Windows 64-bit

Haven't looked at that yet. I'm pretty confident though that we need
libxml2 to be compiled for x64 first.

I use the binaries provided by Igor Zlatkovic
(http://www.zlatkovic.com/libxml.en.html) to build lxml. Maybe you can
get the ball rolling by pinging Igor about providing x64 binaries? I'm
a little bit short of time to start that discussion, but will
eventually need a x64 build myself, for using lxml with IIS in Windows
Server x64.

On Thu, Oct 2, 2008 at 10:56 AM, Hanni Ali <hanni.ali <at> gmail.com> wrote:
> Hi All,
>
> Came across this little gem of a Python module which seems able to translate
> some XML reports for me nicely.
>
> I was very pleased to see a Python 2.6 installer for windows, made checking
> it out much easier than many modules I use. So thanks for that.
>
> However although my testing seems to confirm this is the ideal module I do
> need to deploy to our production environment which is a 64-bit Windows
> environment running Python 2.6 (I code on  32-bit box for
> simplicity/resource reasons).
>
> Has anyone compiled and used lxml on this platform combination? If not does
> anyone foresee me having any issues compiling it for this platform?
>
> Thanks,
>
> Hanni
>
> _______________________________________________
> lxml-dev mailing list
> lxml-dev <at> codespeak.net
> http://codespeak.net/mailman/listinfo/lxml-dev
>
>

--

-- 
Sidnei da Silva
Enfold Systems                http://enfoldsystems.com
Fax +1 832 201 8856     Office +1 713 942 2377 Ext 214
Hanni Ali | 2 Oct 16:10 2008
Picon

Re: Compilation of lxml on Windows 64-bit

OK thanks Sidnei,

I was wondering if you had been using his binaries our compiling you own. Is there an appropriate mailing list or should I ping Igor directly.

I will let you know how usage on 64-bit goes and let you know about any issues.

Cheers,

Hanni


2008/10/2 Sidnei da Silva <sidnei <at> enfoldsystems.com>
Haven't looked at that yet. I'm pretty confident though that we need
libxml2 to be compiled for x64 first.

I use the binaries provided by Igor Zlatkovic
(http://www.zlatkovic.com/libxml.en.html) to build lxml. Maybe you can
get the ball rolling by pinging Igor about providing x64 binaries? I'm
a little bit short of time to start that discussion, but will
eventually need a x64 build myself, for using lxml with IIS in Windows
Server x64.

On Thu, Oct 2, 2008 at 10:56 AM, Hanni Ali <hanni.ali <at> gmail.com> wrote:
> Hi All,
>
> Came across this little gem of a Python module which seems able to translate
> some XML reports for me nicely.
>
> I was very pleased to see a Python 2.6 installer for windows, made checking
> it out much easier than many modules I use. So thanks for that.
>
> However although my testing seems to confirm this is the ideal module I do
> need to deploy to our production environment which is a 64-bit Windows
> environment running Python 2.6 (I code on  32-bit box for
> simplicity/resource reasons).
>
> Has anyone compiled and used lxml on this platform combination? If not does
> anyone foresee me having any issues compiling it for this platform?
>
> Thanks,
>
> Hanni
>
> _______________________________________________
> lxml-dev mailing list
> lxml-dev <at> codespeak.net
> http://codespeak.net/mailman/listinfo/lxml-dev
>
>



--
Sidnei da Silva
Enfold Systems                http://enfoldsystems.com
Fax +1 832 201 8856     Office +1 713 942 2377 Ext 214

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
Hanni Ali | 2 Oct 16:11 2008
Picon

Re: Compilation of lxml on Windows 64-bit

Forget that, found the mailing list.

2008/10/2 Hanni Ali <hanni.ali <at> gmail.com>
OK thanks Sidnei,

I was wondering if you had been using his binaries our compiling you own. Is there an appropriate mailing list or should I ping Igor directly.

I will let you know how usage on 64-bit goes and let you know about any issues.

Cheers,

Hanni


2008/10/2 Sidnei da Silva <sidnei <at> enfoldsystems.com>

Haven't looked at that yet. I'm pretty confident though that we need
libxml2 to be compiled for x64 first.

I use the binaries provided by Igor Zlatkovic
(http://www.zlatkovic.com/libxml.en.html) to build lxml. Maybe you can
get the ball rolling by pinging Igor about providing x64 binaries? I'm
a little bit short of time to start that discussion, but will
eventually need a x64 build myself, for using lxml with IIS in Windows
Server x64.

On Thu, Oct 2, 2008 at 10:56 AM, Hanni Ali <hanni.ali <at> gmail.com> wrote:
> Hi All,
>
> Came across this little gem of a Python module which seems able to translate
> some XML reports for me nicely.
>
> I was very pleased to see a Python 2.6 installer for windows, made checking
> it out much easier than many modules I use. So thanks for that.
>
> However although my testing seems to confirm this is the ideal module I do
> need to deploy to our production environment which is a 64-bit Windows
> environment running Python 2.6 (I code on  32-bit box for
> simplicity/resource reasons).
>
> Has anyone compiled and used lxml on this platform combination? If not does
> anyone foresee me having any issues compiling it for this platform?
>
> Thanks,
>
> Hanni
>
> _______________________________________________
> lxml-dev mailing list
> lxml-dev <at> codespeak.net
> http://codespeak.net/mailman/listinfo/lxml-dev
>
>



--
Sidnei da Silva
Enfold Systems                http://enfoldsystems.com
Fax +1 832 201 8856     Office +1 713 942 2377 Ext 214


_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
Stefan Behnel | 2 Oct 21:26 2008
Picon

Re: Writing TargetParser in Cython

Hi,

Max Ivanov wrote:
> I'm trying to write TargetParser in Cython just to compare perfomance.
> The problem is with data types. If I define data method as "def
> data(self, char *data):" I'm unable to use it as TargetParser. I get
> " def data(self, char *data):
> UnicodeEncodeError: 'ascii' codec can't encode characters in position
> 0-4: ordinal not in range(128)"  error.

That's because you get a unicode string as input, which is not compatible with
a char*.

>     def data(self, char *data):
>         self._data.append(data)

This is actually very inefficient. Cython will generate code here that
retrieves the char* from the Python input string and then creates a new Python
string from it to pass it into the .append() method.

lxml uses a C interface internally, but AFAIR, it's not exposed at the C API
level. Check the sources in parser.pxi and parsertarget.pxi.

Stefan
Dirk Holtwick | 5 Oct 16:22 2008
Picon

Re: Use cssselect.py in Pyxer

Hi,

I thought I answer your mail when I really used it and today it is 
completed ;)

Pyxer now offers a small template language that is quite similar to 
Genshi but works on Google App Engine. The CSSSelector routine makes 
accessing certain parts of the document much easer. Thanks a lot for 
this useful peace of code!

Download: http://pypi.python.org/pypi/pyxer/0.6.0

BTW: Ian, my work started with your great tutorial "Another 
Do-It-Yourself Framework", that was a little treasure of ideas ;) 
http://pythonpaste.org/webob/do-it-yourself.html

Dirk

Ian Bicking schrieb:
> Dirk Holtwick wrote:
>> Hi,
>>
>> I wrote (yet another) templating language for Python based on Genshi, 
>> since Genshi itself does not yet work on Google App Engine (GAE). 
>> Since Genshi supports XPath I was thinking about using your 
>> cssselect.py module together with it. First tests showed that this 
>> seems to work fine.
>>
>> Now I would like to ship a little bit modified version of cssselect.py 
>> with this new templating language called "Pyxer"
>>
>>     http://code.google.com/p/pyxer/
>>
>> so the users do not have to install the whole lxml package (which does 
>> not work with GAE anyways I suppose).
>>
>> Since Python "lxml" is under the BSD license and Pyxer under MIT 
>> license I think this should not be such a big problem as long as I add 
>> your copyright notices to the file. Am I right?
> 
> Of course!  That's open source in action ;)
> 
> You might also find that the intermediate representation for CSS 
> expressions could be turned into a Genshi filter/selector/whatever-it-is 
> of some sort.  Currently there's the objects in cssselect with .xpath() 
> methods -- you could augment them with a .match(markup_obj) method or 
> something along those lines.  Anyway, it might be a useful way to speed 
> it up later.
> 
Hanni Ali | 15 Oct 18:43 2008
Picon

Re: Compilation of lxml on Windows 64-bit

Hi Sidnei,

I have suceeded in compiling some form of libxml2 and libxslt, however I have not been able to use them to compile lxml which I think is due to some issues I have been having with iconv. I have managed to get lxml to compile using the win_iconv I found here:

http://www.gtk.org/download-windows-64bit.html

However the linker throws a whole host of unresolved external symbol errors, would you mind taking a look at the attached file to see if you notice something I'm doing wrong?

Let me know if I can provide anything else which may help.

Kind Regards,

Hanni

2008/10/2 Sidnei da Silva <sidnei <at> enfoldsystems.com>
Haven't looked at that yet. I'm pretty confident though that we need
libxml2 to be compiled for x64 first.

I use the binaries provided by Igor Zlatkovic
(http://www.zlatkovic.com/libxml.en.html) to build lxml. Maybe you can
get the ball rolling by pinging Igor about providing x64 binaries? I'm
a little bit short of time to start that discussion, but will
eventually need a x64 build myself, for using lxml with IIS in Windows
Server x64.

On Thu, Oct 2, 2008 at 10:56 AM, Hanni Ali <hanni.ali <at> gmail.com> wrote:
> Hi All,
>
> Came across this little gem of a Python module which seems able to translate
> some XML reports for me nicely.
>
> I was very pleased to see a Python 2.6 installer for windows, made checking
> it out much easier than many modules I use. So thanks for that.
>
> However although my testing seems to confirm this is the ideal module I do
> need to deploy to our production environment which is a 64-bit Windows
> environment running Python 2.6 (I code on  32-bit box for
> simplicity/resource reasons).
>
> Has anyone compiled and used lxml on this platform combination? If not does
> anyone foresee me having any issues compiling it for this platform?
>
> Thanks,
>
> Hanni
>
> _______________________________________________
> lxml-dev mailing list
> lxml-dev <at> codespeak.net
> http://codespeak.net/mailman/listinfo/lxml-dev
>
>



--
Sidnei da Silva
Enfold Systems                http://enfoldsystems.com
Fax +1 832 201 8856     Office +1 713 942 2377 Ext 214

Attachment (output.zip): application/zip, 4474 bytes
_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev
Stefan Behnel | 15 Oct 19:46 2008
Picon

Re: Simple doctypes not in docinfo.doctype

Hi,

F Wolff wrote:
> I've tried this with an old (1.3.2) and newer (2.0.6) lxml version.
> 
> (this example is roughly based on the code at
> http://codespeak.net/lxml/tutorial.html)
> 
> from lxml import etree
> from StringIO import StringIO
> tree = etree.parse(StringIO("""<!DOCTYPE TS><TS></TS>"""))
> tree.docinfo.doctype
> ''
> 
> From my understanding this DOCTYPE declaration is valid (and occurring
> in the wild in Qt .ts files). My real issue is round-trip problems in a
> reading-writing cycle where the DOCTYPE is lost, but I guess not being
> able to use .docinfo.doctype is already a problem.

I agree that better handling is desirable here. Could you file a bug report so
that this doesn't get lost? (and so that you get notified on any further
development).

https://bugs.launchpad.net/lxml

If you want to give it a try yourself, the DOCTYPE writing code is in
src/lxml/serializer.pxi, function _writeDtdToBuffer(), the docinfo code is in
lxml.etree.pyx, class DocInfo. Patches and test cases
(src/lxml/tests/test_etree.py) are welcome.

Thanks,
Stefan

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev

Gmane