[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-octave-devel] Octave 3.4 FTBFS

On Sun, Dec 25, 2011 at 10:06:32AM +0100, Sébastien Villemot wrote:
> For the 32 versus 64 bit issue, the bulk of the differences comes from
> symbols whose signature changes between the two archs. Typically it’s a
> "long" which becomes a "long long" (as indicated by c++filt). So it is
> not possible to make those optional on either arch.
> I did not investigate all differences though (the file is really big!),
> so there may be some symbols which could be made optional on some
> archs. In particular the 32 bit file has 61 more lines than the 64 bit
> one, so some 32 bit specific symbols can probably me marked as optional
> on all arches. But it will probably be a small minority.
> FYI, here is how I created the arch specific files:
> - starting from the patch which is in the i386 build log on buildd, I
>   grepped the lines starting with a minus sign, and put them in the
>   .64bit file
> - similarly, I put the lines starting with a plus sign in the .32bit
>   file
> - I removed the 64 bit lines from the common file
> For kfreebsd, I also started from the patch in the build log, but I
> manually added arch tags since the changes are small.
> > Anyway, it's Christmas time, so this will not happen today ;)
> >
> > Joyeux Noël 
> Merry Xmas to you too!

Status update: 
I'm working on the ia64 porter box and have marked some more symbols as
optional, following a discussion on the debian-mentors list (the summary
of which is that symbol files for C++ libraries are a gray area):

The majority of differences that is still visible is due to va_list
being a (void*) pointer on ia64, whereas it's a special __va_list_arg*
type on other architectures. 

Anyway, this will take some more days, as I'm short on time.


Reply to: