hieararchy-netattrib/netname-mangle weirdness

[Steve Rencontre]

This is really mind-boggling.

I have a hierarchical design but I want to use flat power net names, so I've set hierarchy-netattrib-mangle to "disabled" in my gnetlistrc and made sure my power symbols have suitable net= attributes.

If I type "gnetlist -o test.net -g allegro top.sch" at a command prompt, it works as expected. If I put that same command in a shell script: ie,

test:
    #!/bin/sh
    gnetlist -o test.net -g allegro top.sch

and then type ./test, the netlist does NOT flatten the power nets, but gives them hierarchical names.

But worse, if I then type,

    ./test >test.log

yes, nothing but redirecting standard output - it works again! Naturally it also works if I try and use strace to see if it's maybe not reading the gnetlistrc file.

This is gEDA 1.9.0, self-built on Fedora 17 64-bit. The prebuilt version in the repo, 1.8.1, doesn't show this weirdness.

[Peter TB Brett (peter-b)]

Hi Steve,

Could you please check what the output of 'gaf config gnetlist hierarchy-traversal' is in each of these contexts?

Thanks!

[Steve Rencontre (q-launchpad-q)]

The command doesn't work. I just get.

ERROR: Configuration does not have group 'gnetlist'.