Re: different debian/symbols for 32 and 64 bit system?
Hi all, I would like to ask one other question here. Let say that I have two different working debian/symbols file; one for i386 and one for amd64 architecture. package.symbols.i386 package.symbols.amd64 Q1: How to care about other architectures which I am not able test? Q2: Should I have in one other symbols file with all symbols? package.symbols regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
On Thu, Jul 23, 2009 at 5:06 AM, Jaromír Mikešmira.mi...@seznam.cz wrote: Working debian symbols files are in attachments. (they are different in the end of them) You have a lot of #MISSING: lines, did the ABI get broken without a SONAME change. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
Od: Paul Wise p...@debian.org JM Working debian symbols files are in attachments. (they are different in the JM end of them) PW You have a lot of #MISSING: lines, did the ABI get broken without a PW SONAME change. Hi, I am not sure if I understand well your question. I've change nothing consciously I create new symbols file ... there were no one before my upgrade. Maybe you can point me somewhere to help me understand. mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
On Thu, Jul 23, 2009 at 6:36 PM, Jaromír Mikešmira.mi...@seznam.cz wrote: I am not sure if I understand well your question. I've change nothing consciously I create new symbols file ... there were no one before my upgrade. Maybe you can point me somewhere to help me understand. Please read libpkg-guide and its two bug reports. I looked at your symbols files and saw lots of lines starting with #MISSING:. This indicates that some symbols have dissappeared from your library at some stage in the history of that symbols file. That means that the ABI changed without a corresponding change in the SONAME. This can be an RC bug in some situations (when the symbol is part of the public ABI, but not when it should never have been public in the first place). http://bugs.debian.org/525782 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
Od: Paul Wise p...@debian.org JM Working debian symbols files are in attachments. (they are different in the JM end of them) PW You have a lot of #MISSING: lines, did the ABI get broken without a PW SONAME change. Hi, I am not sure if I understand well your question. I've change nothing consciously I create new symbols file ... there were no one before my upgrade. Maybe you can point me somewhere to help me understand. mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
On Thu, Jul 23, 2009 at 06:44:13PM +0200, Paul Wise wrote: On Thu, Jul 23, 2009 at 6:36 PM, Jaromír Mikešmira.mi...@seznam.cz wrote: I am not sure if I understand well your question. I've change nothing consciously I create new symbols file ... there were no one before my upgrade. Maybe you can point me somewhere to help me understand. Please read libpkg-guide and its two bug reports. I looked at your symbols files and saw lots of lines starting with #MISSING:. This indicates that some symbols have dissappeared from your library at some stage in the history of that symbols file. That means that the ABI changed without a corresponding change in the SONAME. This can be an RC bug in some situations (when the symbol is part of the public ABI, but not when it should never have been public in the first place). It can also (simply) be that the ABI is different depending on the architecture. Mike -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: different debian/symbols for 32 and 64 bit system?
Od: Paul Wise p...@debian.org PW I looked at your symbols files and saw lots of lines starting with PW #MISSING:. This indicates that some symbols have dissappeared from PW your library at some stage in the history of that symbols file. That PW means that the ABI changed without a corresponding change in the PW SONAME. This can be an RC bug in some situations (when the symbol is PW part of the public ABI, but not when it should never have been public PW in the first place). Hi, I had just one symbols file on beginning. It seems that it was containing all symbols (for both architectures). But some symbols are just for 32-bit and some just for 64-bit systems some for both. Can it be like this? git://git.debian.org/pkg-multimedia/clxclient.git You can check repository for this package if you want I would be pleased by your comments. PWPlease read libpkg-guide and its two bug reports. Thanks for pointing me. regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
different debian/symbols for 32 and 64 bit system?
Hi all, I am upgrading library package here and it seems that dpkg-gensymbols asking different debian/symbols file for my 32bit system and different for 64bit one. Working debian symbols files are in attachments. (they are different in the end of them) Can someone advise me how such issue solve please? regards mira libclxclient.so.3 libclxclient3 #MINVER# _z17clxclient_versi...@base 3.6.1-1~ _zn10x_callbackd...@base 3.6.1-1~ _zn10x_callbackd...@base 3.6.1-1~ _zn13x_scale_style5limi...@base 3.6.1-1~ _zn13x_scale_style7calcpi...@base 3.6.1-1~ _zn13x_scale_style7calcva...@base 3.6.1-1~ _zn5edestd...@base 3.6.1-1~ _zn5edestd...@base 3.6.1-1~ _zn5esyncd...@base 3.6.1-1~ _zn6x_draw10drawpointseip6xpo...@base 3.6.1-1~ _zn6x_draw10drawstringep...@base 3.6.1-1~ _zn6x_draw12drawsegmentseip8xsegm...@base 3.6.1-1~ _zn6x_draw7movepixei...@base 3.6.1-1~ _zn6x_draw7setclipei...@base 3.6.1-1~ _zn6x_draw9drawlineseip6xpo...@base 3.6.1-1~ _zn6x_draw9textwidthe...@base 3.6.1-1~ _zn6x_drawc1ep9_xdisplaymp4_xgcp8_xftd...@base 3.6.1-1~ _zn6x_drawc2ep9_xdisplaymp4_xgcp8_xftd...@base 3.6.1-1~ _zn7x_hints4size...@base 3.6.1-1~ _zn7x_hints5grou...@base 3.6.1-1~ _zn7x_hints5inpu...@base 3.6.1-1~ _zn7x_hints5stat...@base 3.6.1-1~ _zn7x_hints7maxsize...@base 3.6.1-1~ _zn7x_hints7minsize...@base 3.6.1-1~ _zn7x_hints7sizeinc...@base 3.6.1-1~ _zn7x_hints8position...@base 3.6.1-1~ _zn7x_meter12handle_eventep7_xev...@base 3.6.1-1~ _zn7x_meter6exposeep12xexposeev...@base 3.6.1-1~ _zn7x_meter7set_re...@base 3.6.1-1~ _zn7x_meter7set_va...@base 3.6.1-1~ _zn7x_meter8plotsecteiii...@base 3.6.1-1~ _zn7x_meter9plotmarkse...@base 3.6.1-1~ _zn7x_meterc1ep8x_windowp13x_meter_stylep13x_scale_stylei...@base 3.6.1-1~ _zn7x_meterc2ep8x_windowp13x_meter_stylep13x_scale_stylei...@base 3.6.1-1~ _zn7x_meterd...@base 3.6.1-1~ _zn7x_meterd...@base 3.6.1-1~ _zn8h_threadd...@base 3.6.1-1~ _zn8h_threadd...@base 3.6.1-1~ _zn8h_threadd...@base 3.6.1-1~ _zn8itc_ip1q13put_event_try...@base 3.6.1-1~ _zn8itc_ip1q7ipflus...@base 3.6.1-1~ _zn8itc_ip1q9put_eventejp8itc_m...@base 3.6.1-1~ _zn8itc_ip1q9put_event...@base 3.6.1-1~ _zn8itc_ip1qd...@base 3.6.1-1~ _zn8itc_ip1qd...@base 3.6.1-1~ _zn8x_button12handle_eventep7_xev...@base 3.6.1-1~ _zn8x_button6bpressep12xbuttonev...@base 3.6.1-1~ _zn8x_button6exposeep12xexposeev...@base 3.6.1-1~ _zn8x_button6redra...@base 3.6.1-1~ _zn8x_button7releas...@base 3.6.1-1~ _zn8x_button8breleaseep12xbuttonev...@base 3.6.1-1~ _zn8x_button8set_sta...@base 3.6.1-1~ _zn8x_buttonc1ep8x_windowp10x_callbackp14x_button_style...@base 3.6.1-1~ _zn8x_buttonc2ep8x_windowp10x_callbackp14x_button_style...@base 3.6.1-1~ _zn8x_buttond...@base 3.6.1-1~ _zn8x_buttond...@base 3.6.1-1~ _zn8x_buttond...@base 3.6.1-1~ _zn8x_enumip12handle_eventep7_xev...@base 3.6.1-1~ _zn8x_enumip4_x...@base 3.6.1-1~ _zn8x_enumip5cbke...@base 3.6.1-1~ _zn8x_enumip5spkeyep9xkeyev...@base 3.6.1-1~ _zn8x_enumip6bpressep12xbuttonev...@base 3.6.1-1~ _zn8x_enumip6exposeep12xexposeev...@base 3.6.1-1~ _zn8x_enumip6redra...@base 3.6.1-1~ _zn8x_enumip6selec...@base 3.6.1-1~ _zn8x_enumip7set_in...@base 3.6.1-1~ _zn8x_enumip8keypressep9xkeyev...@base 3.6.1-1~ _zn8x_enumip8remfocusep17xfocuschangeev...@base 3.6.1-1~ _zn8x_enumip8setfocusep17xfocuschangeev...@base 3.6.1-1~ _zn8x_enumip9_utf8ma...@base 3.6.1-1~ _zn8x_enumip9textwidth...@base 3.6.1-1~ _zn8x_enumipc1ep8x_windowp10x_callbackp14x_textln_stylep11x_enip_itemp8x_linked...@base 3.6.1-1~ _zn8x_enumipc2ep8x_windowp10x_callbackp14x_textln_stylep11x_enip_itemp8x_linked...@base 3.6.1-1~ _zn8x_enumipd...@base 3.6.1-1~ _zn8x_enumipd...@base 3.6.1-1~ _zn8x_enumipd...@base 3.6.1-1~ _zn8x_hmeter5pmarkep4_x...@base 3.6.1-1~ _zn8x_hmeter5psectep4_xg...@base 3.6.1-1~ _zn8x_hmeterc1ep8x_windowp13x_meter_stylep13x_scale_style...@base 3.6.1-1~ _zn8x_hmeterc2ep8x_windowp13x_meter_stylep13x_scale_style...@base 3.6.1-1~ _zn8x_hmeterd...@base 3.6.1-1~ _zn8x_hmeterd...@base 3.6.1-1~ _zn8x_hscale12handle_eventep7_xev...@base 3.6.1-1~ _zn8x_hscale6exposeep12xexposeev...@base 3.6.1-1~ _zn8x_hscalec1ep8x_windowp13x_scale_stylei...@base 3.6.1-1~ _zn8x_hscalec2ep8x_windowp13x_scale_stylei...@base 3.6.1-1~ _zn8x_hscaled...@base 3.6.1-1~ _zn8x_hscaled...@base 3.6.1-1~ _zn8x_linkedd...@base 3.6.1-1~ _zn8x_linkedd...@base 3.6.1-1~ _zn8x_mclist12handle_eventep7_xev...@base 3.6.1-1~ _zn8x_mclist4bac...@base 3.6.1-1~ _zn8x_mclist4for...@base 3.6.1-1~ _zn8x_mclist4itemepk...@base 3.6.1-1~ _zn8x_mclist4mov...@base 3.6.1-1~ _zn8x_mclist4sho...@base 3.6.1-1~ _zn8x_mclist4sor...@base 3.6.1-1~ _zn8x_mclist6bpressep12xbuttonev...@base 3.6.1-1~ _zn8x_mclist6exposeep12xexposeev...@base 3.6.1-1~ _zn8x_mclist6resize...@base 3.6.1-1~ _zn8x_mclist6updateei...@base 3.6.1-1~ _zn8x_mclistc1ep8x_windowp10x_callbackp14x_mclist_styleiii...@base 3.6.1-1~ _zn8x_mclistc2ep8x_windowp10x_callbackp14x_mclist_styleiii...@base 3.6.1-1~ _zn8x_mclistd...@base 3.6.1-1~
Re: different debian/symbols for 32 and 64 bit system?
On Thu, Jul 23, 2009 at 05:06:54AM +0200, Jaromír Mikeš wrote: Hi all, I am upgrading library package here and it seems that dpkg-gensymbols asking different debian/symbols file for my 32bit system and different for 64bit one. Working debian symbols files are in attachments. (they are different in the end of them) Can someone advise me how such issue solve please? see the dpkg-gensymbols manpage. it explains how to use different symbols files for different architectures. -- _ Ryan Niebur ryanrya...@gmail.com signature.asc Description: Digital signature
Re: Re: different debian/symbols for 32 and 64 bit system?
Od: Ryan Niebur ryanrya...@gmail.com see the dpkg-gensymbols manpage. it explains how to use different symbols files for different architectures. I see it now Thank you.. mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
