xfwm4 version to try [WAS Re: xfce4-session crash]

[Olivier Fourdan]

Ric,

ltcf-c.sh was part of the multi-language-branch of libtool 1.4 that we
were using previously, we use libtool 1.5 now. There is no need for
"ltcf-c.sh" anywore.

Cheers,
Olivier.

On Sun, 2003-07-27 at 09:21, Ric wrote:
> Hi Olivier,
> 
> [The short]
> Well I finally got the latest CVS and sure enough it won't  make rpm  either. 
> The problem is that there is no  ltcf-c.sh  file.
> Would you please check to make sure that the file is in the xfwm4 CVS?  My
> tests indicate that it is not.  It was not in the xfwm4 tarbz2 either.
> 
> [The long]
> I ran a xfdiff for the makefile.in between the 3.99.2 version(which works with
>  make rpm ) and the CVS xfwm4 version:
> 
> --- Makefile.in	2003-07-14 03:32:14.000000000 -0500
> +++ Makefile.in.NEWEST	2003-07-26 20:52:26.000000000 -0500
> @@ -205,7 +205,8 @@
>  DIST_COMMON = README AUTHORS COPYING ChangeLog INSTALL Makefile.am \
>  	Makefile.in NEWS TODO aclocal.m4 compile config.guess \
>  	config.h.in config.sub configure configure.ac depcomp \
> -	install-sh ltmain.sh missing mkinstalldirs xfwm4.spec.in
> +	install-sh ltcf-c.sh ltmain.sh missing mkinstalldirs \
> +	xfwm4.spec.in
>  DIST_SUBDIRS = $(SUBDIRS)
>  all: config.h
>  	$(MAKE) $(AM_MAKEFLAGS) all-recursive
> 
> ===============================
> Somebody (you?) added the  " ltcf-c.sh " to the list but that file is not
> included with the new xfwm4.  Prior to, at least, that change,  make rpm 
> worked for xfwm4 here.  I have not updated CVS for quite a while before today(
> update-xfce and/or cvs kept getting hung on .pot conflicts ...).  Today I used
> cvs co directly rather than update-xfce.
> 
> That's the only related change/diff I found. Just when or why it happened, I
> do not know as the last ChangeLog entry is dated July 19.
> 
> BTW, that  ltcf-c.sh  is in the  xfwm4-3.91.0  from the old targz(i stiil have
> those).  I am going to copy it to the new xfwm4( from CVS ) and try a cvs
> update. Hopefully, it will get any changes. 
> ...
> ... nope, cvs does not know what it is. The response is: " ?
> xfce-devel/xfwm4/ltcf-c.sh "
> 
> It looks like ltcf-c.sh is now missing from the xfwm4 CVS as well as the
> tarbz2.  Of course it is not in some of the other XFce4 files but their
> Makefiles.in do not have the change mentioned above and  make rpm  works for
> them.
> 
> 
> [ BTW, the  make rpm  works with the (old?) ltcf-c.sh that I copied over to
> the new xfwm4 from CVS.  And i was able to install it with --force.  And,
> shortly, will have the rest of CVS installed for testing... i hope. :) ]
> 
> ============
> --- Olivier Fourdan <fourdan at xfce.org> wrote:
> > Ric,
> > 
> > On Fri, 2003-07-25 at 23:51, Ric wrote:
> > > Maybe something else is wrong? 
> > 
> > Yes, something is wrong... The released tarballs are built from the same
> > CVS, and yes, all xfce4 components depend on libtool 1.5 but there's
> > nothing new here, it's been like that before even beta1...
> > Cheers,
> > -- 
> > Olivier Fourdan - fourdan at xfce.org
> 
> 
> 
> 
> 
> =====
> Have A Great Day!
> 
> Ric
> ***
> Thought for today:
> Software is like sex: it's better when it's free.
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> Xfce4-dev mailing list
> Xfce4-dev at xfce.org
> http://moongroup.com/mailman/listinfo/xfce4-dev
-- 
Olivier Fourdan - fourdan at xfce.org
   
   Interoperability is the keyword, uniformity is a dead end. 
   http://www.xfce.org