Building a 64 bit variant of ncurses and gdb?

For a couple of reasons, I'd like to build the ncurses and gdb
packages for sparc64 co-installed with the sparc ones.

That is, I'd like to build

ncurses64-5.2-26.sparc64.rpm
ncurses64-devel-5.2-26.sparc64.rpm
ncurses64-c++-devel-5.2-26

end eventually, if ncurses is possible, a 

gdb64-5.2-2.sparc64.rpm

based on the very same source as is it's currently existing *.sparc.rpm.

My hope is that a similar approach as glibc64 might be possible...

Now, starting with ncurses... we have a concept of /lib -> /lib64 and
/lib -> /usr/lib64, so anything that goes into /usr/lib, should go
into /usr/lib64, i.e., libform, libmenu, libncurses, libpanel, and
libncurses++.

But we have stuff in /usr/bin, such as captoinfo, clear, infocmp etc,
where should I put these? /usr/bin -> /usr/bin64 perhaps? Or, are the
/usr/bin stuff "transparent" to sparc64 issues so that I can make
ncurses64 depend on ncurses being installed and just skip the binaries.

This also goes for stuff in /usr/share... a /usr/share -> /usr/share64
or simply get an understanding that the /usr/share stuff is
transparent to sparc64 issues and depend on the ncurses package being
installed?

What about the stuff in /usr/include (ncurses-devel)? Same thing here,
a /usr/include -> /usr/include64 or get a grip about transparency?

Or maybe forget the whole idea and just try to build in the /usr/local
tree what I need?

I think that eventually, there is a need for a gdb compiled for target
sparc64-linux. That requires a ncurses package built for target
sparc64-linux as far as I have understood so far... So, in a longer
time frame, a sparc64 complemental package of ncurses and gdb might be
"a good idea" (tm).

Cheers,

/ChJ