On Sun, Feb 12, 2012 at 02:37:20PM -0500, Luis Ibanez wrote: > I have now implemented this.
I have seen your svn commit and noticed the change. > The extra files are restored after a "clean" by copying them > back from the helper directory during the configuration stage. Yes. > created a pbuild environment with: > > sudo pbuilder create --distribution sid --debootstrapopts --arch > --debootstrapopts i386 --basetgz /var/cache/pbuilder/base-i386.tgz > --mirror http://ftp.jp.debian.org/debian linux32 > > (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. > I have don't see this specific error. > Hopefully that means that the use of the helper > directory to restore the extra files is doing the trick. > > However, now I'm running on a new error at the > time of building the .c files. > > The message is: > > /usr/include/i386-linux-gnu/asm/posix_types.h:2:30: fatal error: > posix_types_32.h: No such file or directory > > apt-file find tells me that posix_types_32.h is available > in the packages: > > * 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. > 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. > 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 [email protected]. 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. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
