Date: Sun, 17 Feb 2002 13:28:18 -0500 From: Austin Shaw Hall <ash@vectorstar.net> To: gnome@FreeBSD.ORG Subject: Re: can't make gnome-- and gnomespell Message-ID: <20020217132818.A38714@darkstar.bellsouth.net> In-Reply-To: <1013968823.76882.12.camel@shumai.marcuscom.com>; from marcus@marcuscom.com on Sun, Feb 17, 2002 at 01:00:23PM -0500 References: <20020216194752.A22434@darkstar.bellsouth.net> <1013968823.76882.12.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I followed your directions for patching gnome-- and it worked.
I also applied your patch by hand to gnomespell (remember, it was
giving me the same problem) and that worked as well.
Thanks for your help Joe.
On Sunday 17 February Joe Clarke wrote:
> On Sat, 2002-02-16 at 19:47, Austin hall wrote:
> > portupgrade fails configuring gnome-- and gnomespell; my port tree is
> > updated daily and I am running 4.5-stable with XFree86-4.2.0.
> >
> > Here is the output for gnome--:
>
> Try these patches for gnome--. Apply the Makefile.patch to
> /usr/ports/x11-toolkits/gnome--/Makefile. Stick
> patch-scripts::ltmain.sh in /usr/ports/x11-toolkits/gnome--/files. Do a
> make clean install, and see if it works.
>
> Joe
>
> >
> > ===> Configuring for gnomemm-1.2.2
> > loading cache ./config.cache
> > checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
> > checking whether build environment is sane... yes
> > checking whether gmake sets ${MAKE}... (cached) yes
> > checking for working aclocal... found
> > checking for working autoconf... found
> > checking for working automake... found
> > checking for working autoheader... found
> > checking for working makeinfo... found
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > checking for gcc... (cached) cc
> > checking whether the C compiler (cc -O -pipe ) works... yes
> > checking whether the C compiler (cc -O -pipe ) is a cross-compiler... no
> > checking whether we are using GNU C... (cached) yes
> > checking whether cc accepts -g... (cached) yes
> > checking how to run the C preprocessor... (cached) cc -E
> > checking for flex... (cached) flex
> > checking for flex... (cached) flex
> > checking for yywrap in -lfl... (cached) yes
> > checking lex output file root... (cached) lex.yy
> > checking whether yytext is a pointer... (cached) yes
> > checking for bison... (cached) bison -y
> > checking whether gmake sets ${MAKE}... (cached) yes
> > checking host system type... i386--freebsd4.5
> > checking build system type... i386--freebsd4.5
> > checking for ranlib... (cached) ranlib
> > checking for ld used by GCC... (cached) /usr/libexec/elf/ld
> > checking if the linker (/usr/libexec/elf/ld) is GNU ld... (cached) yes
> > checking for BSD-compatible nm... (cached) /usr/bin/nm -B
> > checking whether ln -s works... (cached) yes
> > updating cache ./config.cache
> > ltconfig: too many arguments
> > Try `ltconfig --help' for more information.
> > configure: error: libtool configure failed
> > ===> Script "configure" failed: here are the contents of "config.log"
> > This file contains any messages produced by compilers while
> > running configure, to aid debugging if configure makes a mistake.
> >
> > configure:647: checking for a BSD compatible install
> > configure:700: checking whether build environment is sane
> > configure:757: checking whether gmake sets ${MAKE}
> > configure:803: checking for working aclocal
> > configure:816: checking for working autoconf
> > configure:829: checking for working automake
> > configure:842: checking for working autoheader
> > configure:855: checking for working makeinfo
> > configure:873: checking whether to enable maintainer-specific portions of Makefiles
> > configure:930: checking for gcc
> > configure:1043: checking whether the C compiler (cc -O -pipe ) works
> > configure:1059: cc -o conftest -O -pipe conftest.c 1>&5
> > configure:1085: checking whether the C compiler (cc -O -pipe ) is a cross-compiler
> > configure:1090: checking whether we are using GNU C
> > configure:1118: checking whether cc accepts -g
> > configure:1150: checking how to run the C preprocessor
> > configure:1235: checking for flex
> > configure:1268: checking for flex
> > configure:1302: checking for yywrap in -lfl
> > configure:1344: checking lex output file root
> > configure:1365: checking whether yytext is a pointer
> > configure:1410: checking for bison
> > configure:1441: checking whether gmake sets ${MAKE}
> > configure:1475: checking host system type
> > configure:1567: checking build system type
> > configure:1587: checking for ranlib
> > configure:1626: checking for ld used by GCC
> > configure:1688: checking if the linker (/usr/libexec/elf/ld) is GNU ld
> > configure:1704: checking for BSD-compatible nm
> > configure:1740: checking whether ln -s works
> > (end of "config.log")
> > *** Error code 1
> >
> > Stop in /usr/ports/x11-toolkits/gnome--.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11-toolkits/gnome--.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11-toolkits/gnome--.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11-toolkits/gnome--.
> > *** Error code 1
> >
> > Stop in /usr/ports/x11-toolkits/gnome--.
> > *** Error code 1
> >
> > Thanks.
> > Austin
> > --
> > One is not superior merely because one sees the world as odious.
> > -- Chateaubriand (1768-1848)
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-gnome" in the body of the message
> >
>
Austin
--
"My doctor told me to stop having intimate dinners for four. Unless
there are three other people."
-- Orson Welles
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020217132818.A38714>