Hi Jim,
On Mon, 2008-07-07 at 17:49 +0800, Jim Li wrote:
> > A general comment would be that we are shipping a 64-bit version
> > of gtk+, so we should probably have a 64-bit gtkspell as well,
> > but then we probably need to have a 64-bit SUNWgnome-spell first.
> > I suggest you file a bug against both SUNWgnome-spell and gtkspell
> > so that this won't be forgotten about.
> >
> >
> Can you tell the which package also has this kind of 64-bit stuff for me
> to reference to? Is it OK for me to file a bug about his when
> SUNWgtkspell integrated into Neveda?
There are quite a few. SUNWdbus.spec is a fine example.
spec-files/docs/multi-ISA.txt explains how the whole thing is
supposed to work.
> > This doesn't seem very useful. Since you're setting CXXFLAGS
> > later, I suspect this package includes C++ code, in which
> > case you probably want to set CXX to "$CXX -norunpath" in the %else
> > branch.
I notice you removed the %if %cc_is_gcc thing, so there is no c++
code? If there is, you probably need that to pass -norunpath
through libtool otherwise your binaries will have some extra
directories in their runpath. You can verify with
dump -Lvp <file>.so | grep RUNPATH
However, if there is no C++ code, you don't need this:
> export CXXFLAGS="%cxx_optflags"
Note that your ARC case should also mention if there is C++
code in a shared lib.
Laca
