Error building libncdf

Bug #1676417 reported by Pedro Brandimarte
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Siesta
Fix Released
High
Nick Papior
4.1
Fix Released
High
Nick Papior

Bug Description

I got an error when trying to compile trunk-612:

ncdf-build:
ncdf-build: FDICT_PREFIX is not defined, we default to the internal one
ncdf-build:
Makefile:4: *** missing separator. Stop.
make[1]: Leaving directory 'xxxxxxxxx/Obj/ncdf/obj'
make: *** [Makefile:358: libncdf.a] Error 2

I think this can be fix by including -e option after echo at line 361 at the main Makefile so then th tab will work:

        echo -e "\t-cp ../../fdict/obj/settings.bash ." >> Makefile ; \

Revision history for this message
Nick Papior (nickpapior) wrote :

Thanks, I am guessing you are using bash < 4? Something like 3.X?

I am not that keen on adding a flag for `echo`, sadly echo is a rather "unstable" shell command. This was my oversight in using the tabulator.

Could you try with this patch and see if it works in your shell? printf should be much more stable.

Changed in siesta:
importance: Undecided → Critical
importance: Critical → High
assignee: nobody → Nick Papior (nickpapior)
status: New → In Progress
Revision history for this message
Pedro Brandimarte (brandimarte) wrote :

Actually I'm using bash 4.4.12 and the patch worked for me!

Another minor thing (maybe I should open a new thread...), when trying to compile in a cluster with SUSE server it tries to find a suse.make file. From now on one should specify the VENDOR flag at arch.make?

Revision history for this message
Nick Papior (nickpapior) wrote : Re: [Bug 1676417] Re: Error building libncdf

Could you attach the output?

On 28 Mar 2017 10:25, "Pedro Brandimarte" <email address hidden> wrote:

> Actually I'm using bash 4.4.12 and the patch worked for me!
>
> Another minor thing (maybe I should open a new thread...), when trying
> to compile in a cluster with SUSE server it tries to find a suse.make
> file. From now on one should specify the VENDOR flag at arch.make?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1676417
>
> Title:
> Error building libncdf
>
> Status in Siesta:
> In Progress
>
> Bug description:
> I got an error when trying to compile trunk-612:
>
> ncdf-build:
> ncdf-build: FDICT_PREFIX is not defined, we default to the internal one
> ncdf-build:
> Makefile:4: *** missing separator. Stop.
> make[1]: Leaving directory 'xxxxxxxxx/Obj/ncdf/obj'
> make: *** [Makefile:358: libncdf.a] Error 2
>
> I think this can be fix by including -e option after echo at line 361
> at the main Makefile so then th tab will work:
>
> echo -e "\t-cp ../../fdict/obj/settings.bash ." >> Makefile ;
> \
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/siesta/+bug/1676417/+subscriptions
>

Revision history for this message
Nick Papior (nickpapior) wrote :

And no, the VENDOR flag is/should not required in the arch.make file. :)

Revision history for this message
Nick Papior (nickpapior) wrote :

In fact, I am guessing you have VENDOR in your environment variables?

Do

env | grep VENDOR

to check this.
Could you try and compile with:

unset VENDOR && make

Revision history for this message
Pedro Brandimarte (brandimarte) wrote :

Here it is:

make[1]: *** No rule to make target `xxxxxxxxxx/Src/fdict/smeka/vendor/suse.make'. Stop.
make[1]: Leaving directory `xxxxxxxxxxxx/Obj/fdict/obj'
make: *** [libfdict.a] Error 2

And yes, you got it, there is a VENDOR=suse environmental variable setup in the cluster. By doing the following the compilaton went until the end:

unsetenv VENDOR && make

Thanks!

Revision history for this message
Nick Papior (nickpapior) wrote :

I see, but if you use unsetenv you are in csh? I guess this is why. Well, it is fixed with the patch. :)

Thanks.

Changed in siesta:
status: In Progress → Fix Committed
milestone: none → 4.1-b3
Revision history for this message
Pedro Brandimarte (brandimarte) wrote :

Exactly, in the cluster it is csh. In my personal computer where I got the error reported first it is bash though.

Thanks!

Nick Papior (nickpapior)
Changed in siesta:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.