Re: Having idl compile problems on Solaris

[jacob berkman <jacob ximian com>]

On Wed, 2002-07-10 at 11:04, Peter O'Shea wrote:
> jacob berkman wrote:
> 
> >On Tue, 2002-07-09 at 17:58, Peter O'Shea wrote:
> >  
> >
> >>I'm trying to compile nautilus 2.0.0 on a Solaris 8 ultrasparc.  All 
> >>other gnome2 packages have compiled
> >>pretty smoothly, with the exception of problems with 
> >>bind_textdomain_codeset.  I'm installing gnome2
> >>under my home directory, so am configuring with --prefix, but nothing else.
> >>
> >>Compiling nautilus fails in /libnautilus with the two idl files.  I'm 
> >>thinking that my installation of
> >>orbit-idl-2 works ok, because other gnome components with idl compile 
> >>fine.  Below is the command
> >>line output for the first idl file.  Any pointers or help would be 
> >>greatly appreciated.
> >>
> >>Peter O'Shea
> >>
> >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>
> >>/home/poshea/bin/gnome2/bin/orbit-idl-2 
> >>/home/poshea/bin/gnome2/share/idl/bonobo-activation-2.0 
> >>/home/poshea/bin/gnome2/share/idl/bonobo-2.0 
> >>--define=__nautilus_view_component_COMPILATION nautilus-view-component.idl
> >>orbit-idl-2 2.4.0 compiling
> >> small mode, show preprocessor errors, passes: stubs skels common 
> >>headers skel_impl imodule
> >>
> >>cpp: Input file `' is a directory
> >>Error: Empty file
> >>
> >>** (process:16509): WARNING **: 
> >>/home/poshea/bin/gnome2/share/idl/bonobo-activation-2.0 compilation failed
> >>cpp: Input file `' is a directory
> >>Error: Empty file
> >>    
> >>
> >
> >this looks a bit like what i was getting on os x.
> >
> >what does grep IDL_INCLUDES config.status give in the top srcdir for
> >nautilus?  does it work when using gnu sed?
> >
> > - jacob
> >  
> >
> 
> in the nautilus top directory, 'grep IDL_INCLUDES config.status' returns:
> 
> s,@LIBNAUTILUS_IDL_INCLUDES@, 
> /home/poshea/bin/gnome2/share/idl/bonobo-activation-2.0 
> /home/poshea/bin/gnome2/share/idl/bonobo-2.0,;t t
> s,@CORE_IDL_INCLUDES@, 
> /home/poshea/bin/gnome2/share/idl/bonobo-activation-2.0 
> /home/poshea/bin/gnome2/share/idl/bonobo-2.0,;t t
> 
> Where/when would I use gnu sed?

ok, yeah this is the same thing i was running into.  you should make
sure a gnu sed is in your path before the system sed, and re-run
autogen.sh/configure, or just edit config.status and add a -I before the
/home... paths, then run ./config.status.

this is now filed as bug #87835, feel free to add yourself to the Cc.

 - jacob