Re: Proable multiarch related problem in finding header file (Was: Problem finding "posix_types_32.h" when using pbuilder on the fis-gtm package)
Mathieu,
Thanks for the hint,
This is what "dpkg --status pbuilder" reports in the
VM where I'm building the fis-gtm package:
$ dpkg --status pbuilder
Package: pbuilder
Status: install ok installed
Priority: extra
Section: devel
Installed-Size: 1212
Maintainer: Debian pbuilder maintenance team
<pbuilder-maint@lists.alioth.debian.org>
Architecture: all
Version: 0.199+nmu1squeeze1
Depends: debootstrap | cdebootstrap, wget, debianutils (>= 1.13.1),
coreutils (>= 4.5.8-1), debconf (>= 0.5) | debconf-2.0
Recommends: fakeroot, sudo, devscripts
Suggests: pbuilder-uml, gdebi-core, cowdancer
Conffiles:
/etc/bash_completion.d/pbuilder 6af3c8c99796ab77971de5ffac83a0f8
/etc/pbuilder/buildd-config.sh 48b942cabcc5fcfe94f28538239573ba
...
Is this an old version ?
Thanks
Luis
-------------------------
On Tue, Feb 14, 2012 at 3:47 AM, Mathieu Malaterre
<mathieu.malaterre@gmail.com> wrote:
> Andreas,
>
> Doing a quick check on packages.d.o I can see the file your are
> talking about. However:
>
> http://packages.debian.org/search?suite=sid&arch=any&mode=path&searchon=contents&keywords=posix_types.h
>
> returns an empty list. Are you sure your pbuilder is up to date ?
>
> 2cts
>
> On Mon, Feb 13, 2012 at 1:42 PM, Andreas Tille <andreas@an3as.eu> wrote:
>> Hi,
>>
>> just a comment on this: I suspect a multiarch issue and
>>
>> http://lists.debian.org/debian-devel-announce/2011/06/msg00002.html
>>
>> "Multiarch handling of header files (/usr/include) will require
>> more per-package attention, ..."
>>
>> so Luis is asking for some hints how to deal with this like the need to
>> specify explicite header search path via -I options or something like
>> this. Any more detailed hint than the above would be helpful.
>>
>> Kind regards
>>
>> Andreas.
>>
>> On Sun, Feb 12, 2012 at 05:14:47PM -0500, Luis Ibanez wrote:
>>> Debian-mentors,
>>>
>>>
>>> I'm working on packaging fis-gtm,
>>>
>>>
>>> The configuration files that I'm using are here:
>>>
>>> svn+ssh://svn.debian.org/svn/debian-med/trunk/packages/fis-gtm/fis-gtm/trunk/debian
>>>
>>> http://anonscm.debian.org/viewvc/debian-med/trunk/packages/fis-gtm/fis-gtm/trunk/debian/
>>>
>>> These are setup to get the tarball by using:
>>>
>>> uscan --verbose --force-depends
>>>
>>> I manage to build the package locally by using "debuild",
>>> but, when I use the "pdebuild" command, I get the following
>>> output:
>>>
>>>
>>> ----- Start the build -----
>>> Linux Host 32
>>> Linux Host linux i386 x86_regs
>>> Source Directory List: sr_linux sr_i386 sr_x86_regs sr_unix_gnp
>>> sr_unix_cm sr_unix_nsb sr_unix sr_port_cm sr_port
>>> make[2]: Entering directory `/tmp/buildd/fis-gtm-5.4-002B'
>>> mkdir -p /tmp/buildd/fis-gtm-5.4-002B/pro/map
>>> tcsh -f /tmp/buildd/fis-gtm-5.4-002B/sr_unix/gen_gtm_threadgbl_deftypes.csh
>>> /tmp/buildd/fis-gtm-5.4-002B sr_port pro/obj sr_linux sr_i386
>>> sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix_nsb sr_unix sr_port_cm
>>> sr_port
>>> Entering gen_gtm_threadgbl_deftypes.csh to build gtm_threadgbl_deftypes.h
>>> ~/fis-gtm-5.4-002B/pro/obj ~/fis-gtm-5.4-002B
>>> Replacing /tmp/buildd/fis-gtm-5.4-002B/sr_linux/gtm_threadgbl_deftypes.h
>>> ~/fis-gtm-5.4-002B
>>> Exiting gen_gtm_threadgbl_deftypes.csh
>>> make -C /tmp/buildd/fis-gtm-5.4-002B/pro/obj
>>> -I/tmp/buildd/fis-gtm-5.4-002B/pro/obj
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_linux
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_i386
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_x86_regs
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_unix_gnp
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_unix_cm
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_unix_nsb
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_unix
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_port_cm
>>> -I/tmp/buildd/fis-gtm-5.4-002B/sr_port -f
>>> /tmp/buildd/fis-gtm-5.4-002B/sr_unix/comlist.mk CURRENT_BUILDTYPE=pro
>>> all
>>> Linux Host 32
>>> Linux Host linux i386 x86_regs
>>> Source Directory List: sr_linux sr_i386 sr_x86_regs sr_unix_gnp
>>> sr_unix_cm sr_unix_nsb sr_unix sr_port_cm sr_port
>>> make[3]: Entering directory `/tmp/buildd/fis-gtm-5.4-002B/pro/obj'
>>> cc1: note: obsolete option -I- used, please use -iquote instead
>>> /usr/include/i386-linux-gnu/asm/posix_types.h:2:30: fatal error:
>>> posix_types_32.h: No such file or directory
>>> compilation terminated.
>>> cc1: note: obsolete option -I- used, please use -iquote instead
>>> cc1: note: obsolete option -I- used, please use -iquote instead
>>> /usr/include/i386-linux-gnu/asm/posix_types.h:2:30: fatal error:
>>> posix_types_32.h: No such file or directory
>>> compilation terminated.
>>> ...
>>>
>>> and goes on an on,
>>> repeating the error about posix_types_32.h.
>>>
>>>
>>> BTW: Please disregard the message:
>>>
>>> "cc1: note: obsolete option -I- used, please use -iquote instead"
>>>
>>>
>>> This is a known issue, and probably not related to the
>>> problem with posix_types_32.h. I get the same cc1
>>> warnings when building with "dbuild" and yet in that
>>> case the build is successful.
>>>
>>> I'm doing this in a Virtual Machine,
>>> in which "uname -a" returns:
>>> Linux debian-med 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
>>>
>>> The host of this VM, returns for "uname -a":
>>> Linux macondo 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC
>>> 2012 x86_64 GNU/Linux
>>>
>>>
>>> Login into pbuilder, it was possible to verify
>>> that the header file is actually there, under:
>>>
>>> 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
>>>
>>> I'm having trouble understanding why
>>> is that the build process finds:
>>>
>>> ./usr/include/i386-linux-gnu/asm/posix_types.h
>>>
>>> but fails to find
>>>
>>> "posix_types_32.h"
>>>
>>>
>>> Any suggestions will be appreciated,
>>>
>>>
>>> Thanks
>>>
>>>
>>> Luis
>>>
>>>
>>> --
>>> To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
>>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>>> Archive: [🔎] CABAUzPrbxVinePvNkjtGcObgOBF83UkuY8DVxcY8a7i4yj5P0g@mail.gmail.com">http://lists.debian.org/[🔎] CABAUzPrbxVinePvNkjtGcObgOBF83UkuY8DVxcY8a7i4yj5P0g@mail.gmail.com
>>>
>>>
>>
>> --
>> http://fam-tille.de
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: [🔎] 20120213124209.GG24744@an3as.eu">http://lists.debian.org/[🔎] 20120213124209.GG24744@an3as.eu
>>
>
>
>
> --
> Mathieu
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/CA+7wUszhEXDes-oAvviG4iYmHLCXcYHenRZMC+RkNQ+M4Rw@mail.gmail.com
>
Reply to: