Re: [MoM] Packaging fis-get
On Thu, Feb 9, 2012 at 2:12 AM, Andreas Tille <andreas@an3as.eu> wrote:
> Hi Luis,
>
>> Yes,
>> I can replicate this problem here, when I do "debuild".
>>
>> However, when I call directly: tcsh setupenv.sh
>
> Not for me:
>
>
> $ tcsh setupenv.sh
> ----- Start the build -----
> Linux Host 64
> Linux Host linux x86_64 x86_regs
> Source Directory List: sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
> tcsh -f /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/sr_unix/gen_xfer_desc.csh sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
> ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj
> ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj
> tcsh -f /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/sr_unix/gen_gtm_threadgbl_deftypes.csh /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B sr_port pro/obj sr_linux sr_x86_64 sr_x86_regs sr_unix_gnp sr_unix_cm sr_unix sr_port_cm sr_port
> Entering gen_gtm_threadgbl_deftypes.csh to build gtm_threadgbl_deftypes.h
> ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B
> gen_gtm_threadgbl_deftypes.csh-E-: pro build link of /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj/gtm_threadgbl_deftypes failed, see /home/andreas/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B/pro/obj/gtm_threadgbl_deftypes_linkmap.txt
> ~/debian-maintain/repack/fis-gtm/fis-gtm/fis-gtm-5.4-002B
> make: *** [gtm_threadgbl_deftypes] Fehler 1
> ------ End of build -------
>
> (sorry for German locale "Fehler" = "error")
>
It would seem that it is not finding the "extra" files..
The file: gtm_threadgbl_deftypes.h
is one of the files generated by mumps, that we
put in the "extra" tar.gz file. It appears in two places:
fis-gtm/pro/obj/gtm_threadgbl_deftypes.h
fis-gtm/sr_linux/gtm_threadgbl_deftypes.h
>> the build proceeds as expected,
>> and finishes successfully.
>>
>> So, I need to study "debuild" more, to understand what
>> is different by the time "tcsh setupenv.sh" is called.
>
> I do not see a reason why this should be different. The only reason
> might be some preset environment variables.
>
Yes,
the environment seems to be the clearest suspect.
I'll track this...
Luis
Reply to: