Re: Re: Finding the correct alignment for all architectures

2016-10-30 Thread Thomas Weber
Thanks guys, I went with _Alignof(double), which interestingly aligns to 8 bytes on amd64. Thomas

Finding the correct alignment for all architectures

2016-10-12 Thread Thomas Weber
Hi, I am maintaining lcms2. In #749975, I received a patch to ensure correct alignment for doubles von MIPS. I have forwarded the patch upstream[1], but in the latest release, upstream has chosen a different way. It is now possible to configure the alignment via a preprocessor variable

Re: Symbols and C++ inline constructor

2012-01-07 Thread Thomas Weber
On Fri, Jan 06, 2012 at 05:14:32PM -0800, Russ Allbery wrote: Thomas Weber twe...@debian.org writes: On Fri, Jan 06, 2012 at 12:14:11AM +, Roger Leigh wrote: IIRC inline is only a hint--it's not guaranteed to be inlined if the compiler thinks it's more efficient

Re: Symbols and C++ inline constructor

2012-01-06 Thread Thomas Weber
On Fri, Jan 06, 2012 at 12:14:11AM +, Roger Leigh wrote: On Thu, Jan 05, 2012 at 11:46:26PM +0100, Thomas Weber wrote: Hi, I have a question about an inline constructor and debian/symbols. The code looks like this: class X { public: X() { some code

Symbols and C++ inline constructor

2012-01-05 Thread Thomas Weber
Hi, I have a question about an inline constructor and debian/symbols. The code looks like this: class X { public: X() { some code }; } According to http://gcc.gnu.org/onlinedocs/gcc/Inline.html, this means that the constructor is inlined. So, can I mark such a

Re: Overwriting binary files when building a package

2011-12-12 Thread Thomas Weber
On Mon, Dec 12, 2011 at 12:25:08PM +0100, Bernhard R. Link wrote: * Thomas Weber twe...@debian.org [111211 22:08]: my upstream ships documentation in PDF format in the normal sources. Upon build, I re-create those files[1]. The newly generated PDF files differ from the originally shipped

Overwriting binary files when building a package

2011-12-11 Thread Thomas Weber
Hi, my upstream ships documentation in PDF format in the normal sources. Upon build, I re-create those files[1]. The newly generated PDF files differ from the originally shipped ones. So, I have a problem asserting that debian/rules clean gives me the same source tree as dpkg-source -x which

Re: How to maintain a large symbols file of a C++ library

2011-11-21 Thread Thomas Weber
On Wed, Nov 16, 2011 at 10:32:22AM +0100, bastien ROUCARIES wrote: Le Tuesday 8 November 2011 23:47:56, Thomas Weber a écrit : On Tue, Nov 08, 2011 at 12:21:16PM +0100, roucaries bastien wrote: On Tue, Nov 8, 2011 at 12:18 AM, Thomas Weber twe...@debian.org wrote: Hi, I'm

Re: How to maintain a large symbols file of a C++ library

2011-11-08 Thread Thomas Weber
On Tue, Nov 08, 2011 at 12:21:16PM +0100, roucaries bastien wrote: On Tue, Nov 8, 2011 at 12:18 AM, Thomas Weber twe...@debian.org wrote: Hi, I'm in the process of converting Debian's Octave packages into a structure with proper library packaging. The symbols file of these three C

How to maintain a large symbols file of a C++ library

2011-11-07 Thread Thomas Weber
Hi, I'm in the process of converting Debian's Octave packages into a structure with proper library packaging. The symbols file of these three C++ libraries has about 30k lines. I'm pretty new to symbols handling, so I'm looking for advice on how to handle this. Is there a simple way to reduce

Packaging a library -- looking for documentation

2010-01-31 Thread Thomas Weber
Hi, I maintain Octave in Debian. My upstream will switch to using libtool in the next major release (ETA of that release is unknown, but somewhen in 2010). In order to not screw up too badly, I'm looking for documentation on developing/packaging libraries (both from a developer's view and a

Re: Uploads to experimental instead of unstable

2008-12-11 Thread Thomas Weber
Am Donnerstag, den 11.12.2008, 13:09 + schrieb Neil Williams: On Thu, 11 Dec 2008 12:43:03 +0100 Sandro Tosi [EMAIL PROTECTED] wrote: It would make things easier to release Lenny if all (or very nearly all) activities in unstable that were unrelated to the release *were* actually stopped.

Re: Quilt and patches directory

2008-09-14 Thread Thomas Weber
On Sun, Sep 14, 2008 at 04:00:18PM +0200, Andreas Schildbach wrote: Is there any way to tell quilt about the debian package structure? The way it works, it always looks in the current directory for the patches and .pc directories. What I'd like it to do is find the debian directory in the

Re: RFS: QtOctave -- A Qt front-end to Octave

2007-06-18 Thread Thomas Weber
Hi Jordi, Am Montag, 18. Juni 2007 04:38 schrieb Jordi Gutierrez Hermoso: The Debianised source tarball is found here: http://www.cimat.mx/~jordi/debian/qtoctave_0.5.1-1.debian.tar.gz There's something wrong with the tarball. According to the .dsc file: 04dd905a3bb001516045fc06eff46085

Re: Prompt to install missing software?

2007-05-27 Thread Thomas Weber
Hi, Am Sonntag, 27. Mai 2007 06:17 schrieb John Pye: Is there any way under Debian (and hopefully also Ubuntu) that I can trigger gtk-debi or something like that when the user requests to use the part of my program that depends on stuff they haven't installed yet? What would be the best way

Problem with really long argument list to dpkg-shlibdeps

2006-11-14 Thread Thomas Weber
Hi, [no need to CC me, I'm subscribed]. I'm trying to package Octaviz and I'm running into problems with dpkg-shlibdeps. The package generates around 1000 binary modules/plugins. Running dpkg-shlibdeps over these files makes for really weird errors[1], due to the length of the command line

Re: pbuilder outside inside chroot hook scripts

2006-07-24 Thread Thomas Weber
Hi, Workaround: use a simple D hook script [1] to access via http method of apt needed build depends which are stored in manually prepared apt repo (well, on the same machine). Have a look at pbuilder's OTHERMIRROR option (for http and ftp repositories). Improvement?: I think the

two different packages with the same source tarball/name

2006-07-14 Thread Thomas Weber
Hi, is it possible to have two different binary packages with the same source package name (but different upstream versions of the source)? Reason: I'm about to package octave-forge for both Octave 2.1 and 2.9 (you can consider octave-forge as plugin, that needs to be compiled for the