Re: [MoM] Packaging fis-get
On Sun, Feb 12, 2012 at 3:51 PM, Andreas Tille <andreas@an3as.eu> wrote:
>>
>> (Did this to ensure that the environment is a 32 bits one...)
>
> While I do not think that this is wrong and just for the sake of
> interest: Do you have any specific reason to force 32bit? I think
> amd64 would work as well. Pbuilder usually creates the architecture
> you are running at.
>
Not particular reason...
I was circling around the suspicion that this was
a problem related to a 32/64 bits mismatch, and
since the missing file is a 32 bits one, I guessed
that maybe I had to create a 32bit pbuilder
environment. It turned out that I get the same
error in both environments (32 and 64).
>>
>> * linux-libc-dev
>> * gcc-multilib
>>
>> So I added both to the Build-Depends: field
>> in the control file, but to not effect...
>
> IMHO, both is not really needed. I somehow fear some multiarch issue
> and I admit I'm not very knowledged in this.
>
You are most likely right.
Adding these packages didn't make a difference.
It looks like the posix_types_32.h file is indeed
installed in the pbuilder environment, but that its
path is not in the list of the ones used by the
makefiles of fis-gtm.
>> The field (in my local copy) now is:
>>
>> Build-Depends: debhelper (>= 8), adduser, ucf, po-debconf, libicu-dev,
>> tcsh, gnupg, zlib1g-dev, libncurses-dev, libgcrypt11-dev,
>> libgpgme11-dev, linux-libc-dev, gcc-multilib
>
> Without having tested it really my guess is that the both packages are
> installed because of implicite dependencies.
>
Yes, that seems to be the case.
When login in to the pbuilder environment with:
sudo pbuilder --execute /usr/share/doc/pbuilder/examples/C10shell
I can check the following:
With the command:
sudo pbuilder --login --basetgz /var/cache/pbuilder/base.tgz
root@debian-med:/# ls ./usr/include/i386-linux-gnu/asm/posix* -l
-rw-r--r-- 1 root root 92 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types.h
-rw-r--r-- 1 root root 1316 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types_32.h
-rw-r--r-- 1 root root 1306 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types_64.h
root@debian-med:/# uname -a
Linux debian-med 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
When doing this in the 32bits one, with :
linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz
ls ./usr/include/i386-linux-gnu/asm/posix* -l
-rw-r--r-- 1 root root 92 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types.h
-rw-r--r-- 1 root root 1316 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types_32.h
-rw-r--r-- 1 root root 1306 Feb 6 01:32
./usr/include/i386-linux-gnu/asm/posix_types_64.h
root@debian-med:/# uname -a
Linux debian-med 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
>> I'm running out of ideas on how to address this...
>>
>> It seems to be related to a 32 bits, 64 bits mismatch somewhere..
>
> I agree with this suspicion and because I admit that I do not feel able
> to gove technical advise. If I'm confronted with problems like these I
> usually consult the mailing list debian-mentors@lists.debian.org. Just
> Give a link to the packaging stuff in SVN, mention explicitely to get the
> tarball via
>
> uscan --verbose --force-depends
>
> and post the error message you are getting. I'm also reading the list
> and will try to clarify if needed.
>
Good idea,
I just wrote to debian-mentors.
In the meantime,
I'm trying to make some progress
on the installation step...
There, I think that main question will be:
Where should all these executables and files go ?
In the default installation of GTM, the full
collection of files go to:
/usr/lib/fis-gtm/V5.4-002B_x86_64
and they do not get to be included in the path.
Users are instructed to create aliases to these
executables in their .bashrc files.
It would seem however, that in a Debian installation
at least the "gtm" file:
/usr/lib/fis-gtm/V5.4-002B_x86_64/gtm
should be symlinked to /usr/bin, or /usr/local/bin,
to be found as part of the normal path.
Any suggestions ?
Thanks
Luis
Reply to: