From owner-freebsd-x11@FreeBSD.ORG Fri May 11 23:00:54 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5657616A400 for ; Fri, 11 May 2007 23:00:54 +0000 (UTC) (envelope-from freebsd@ruomad.net) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.freebsd.org (Postfix) with ESMTP id D37BA13C45D for ; Fri, 11 May 2007 23:00:53 +0000 (UTC) (envelope-from freebsd@ruomad.net) Received: from [192.168.0.100] (vln78-1-82-238-160-33.fbx.proxad.net [82.238.160.33]) by smtp2-g19.free.fr (Postfix) with ESMTP id C231496198; Sat, 12 May 2007 01:00:52 +0200 (CEST) Message-ID: <4644F5A4.9060709@ruomad.net> Date: Sat, 12 May 2007 01:00:52 +0200 From: Bruno Damour User-Agent: Thunderbird 1.5.0.10 (X11/20070309) MIME-Version: 1.0 To: Kris Kennaway References: <46424D23.9030704@ruomad.net> <46424DF2.7090407@ruomad.net> <20070509230724.GA65588@xor.obsecurity.org> <4642A5A6.3060501@ruomad.net> <20070510053123.GA76390@xor.obsecurity.org> <4642B285.4010904@ruomad.net> <20070510064024.GB76390@xor.obsecurity.org> <4644EBB5.9010302@ruomad.net> <20070511222206.GA33341@xor.obsecurity.org> <4644ED8C.8000709@ruomad.net> <20070511223215.GA33833@xor.obsecurity.org> In-Reply-To: <20070511223215.GA33833@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org Subject: Re: beryl compile fails X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 23:00:54 -0000 Kris Kennaway wrote: > On Sat, May 12, 2007 at 12:26:20AM +0200, Bruno Damour wrote: > >> Kris Kennaway wrote: >>> On Sat, May 12, 2007 at 12:18:29AM +0200, Bruno Damour wrote: >>> >>>> Kris Kennaway wrote: >>>> >>>>> On Thu, May 10, 2007 at 07:49:57AM +0200, Bruno Damour wrote: >>>>> >>>>> >>>>>> Kris Kennaway wrote: >>>>>> >>>>>> >>>>>>> On Thu, May 10, 2007 at 06:55:02AM +0200, Bruno Damour wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Kris Kennaway wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Thu, May 10, 2007 at 12:40:50AM +0200, Bruno Damour wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> Bruno Damour wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Hello >>>>>>>>>>> I"m using the up-to-date git repository. >>>>>>>>>>> trying to build beryl-core fails with (in libberyldecoration): >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> Users who have been tracking git for a while may need to rebuild from >>>>>>>>> scratch to make sure everything is in a sane state. We have not put >>>>>>>>> any work into ensuring that the upgrade path from old git >>>>>>>>> installations is clean. >>>>>>>>> >>>>>>>>> Kris >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> OK I will try to rebuild every thing. >>>>>>>> Any simple procedure to do that and be sure not to forget anything ? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> portupgrade -fa >>>>>>> >>>>>>> Sorry, that will take a while, but unless you can debug the cause >>>>>>> yourself (note that this port built correctly on my tests) this is the >>>>>>> only way we can be sure it's not because of old git stuff that wasn't >>>>>>> updated properly on your system. >>>>>>> >>>>>>> Kris >>>>>>> >>>>>>> >>>>>>> >>>>>> Well, I'll do that, but I already rebuilt quite a lot of things because >>>>>> of the switch from X11BASE to LOCALBASE >>>>>> >>>>>> >>>>> I'm guessing not everything or it would have found the headers ;-) >>>>> >>>>> Kris >>>>> >>>>> >>>> Well I did try portupgrade -fa and portupgrade -fak and I get a lot of >>>> these : >>>> >>>> configure: creating ./config.status >>>> config.status: error: cannot find input file: >>>> ===> Script "configure" failed unexpectedly. >>>> Please report the problem to x11@FreeBSD.org [maintainer] and attach the >>>> "/usr/ports/x11-wm/twm/work/twm-1.0.3/config.log" including the output >>>> of the >>>> failure of your make command. Also, it might be a good idea to provide an >>>> overview of all packages installed on your system (e.g. an `ls >>>> /var/db/pkg`). >>>> *** Error code 1 >>>> >>>> pkg_delete also fails with >>>> >>>> ===> twm-1.0.3_3 has a different PREFIX: /usr/X11R6, skipping >>>> >>>> so I have to do : >>>> pkg_delete -p /usr/X11R6 -f twm >>>> >>>> but reinstalling fails anyway >>>> >>>> Any idea ? >>>> >>> Yeah, you definitely have a broken hybrid system that was not properly >>> updated after X moved into /usr/local. pkg_delete -f and start over. >>> >>> Kris >>> >> which pkgs should I delete ? not ALL ports I hope ? > > Depends how much you can figure out on your own. If you don't want to > do any work, then yes, all of them -- otherwise, figure out which ones > really need to be rebuilt and do those. > > Kris > well I have (surely there is smthg very wrong : vil1 libtool15 # make configure ===> Vulnerability check disabled, database not found ===> Extracting for libtool-1.5.22_4 => MD5 Checksum OK for libtool-1.5.22.tar.gz. => SHA256 Checksum OK for libtool-1.5.22.tar.gz. ===> Patching for libtool-1.5.22_4 ===> Applying FreeBSD patches for libtool-1.5.22_4 ===> Configuring for libtool-1.5.22_4 configure: WARNING: you should use --build, --host, --target checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... none checking for a sed that does not truncate output... /usr/bin/sed checking build system type... amd64-unknown-freebsd7.0 checking host system type... amd64-unknown-freebsd7.0 checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... none checking for g77... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether f77 accepts -g... yes checking for gcj... no checking for windres... no checking for /usr/bin/ld option to reload object files... -r checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking how to run the C++ preprocessor... g++ -E checking the maximum length of command line arguments... 196608 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... freebsd7.0 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking for shl_load... no checking for shl_load in -ldld... no checking for dlopen... yes checking whether a program can dlopen itself... yes checking whether a statically linked program can dlopen itself... no checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd7.0 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for f77 option to produce PIC... -fPIC checking if f77 PIC flag -fPIC works... yes checking if f77 static flag -static works... yes checking if f77 supports -c -o file.o... yes checking whether the f77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd7.0 ld.so checking how to hardcode library paths into programs... immediate appending configuration tag "GCJ" to libtool configure: creating ./config.status config.status: error: cannot find input file: ===> Script "configure" failed unexpectedly. Please report the problem to ade@FreeBSD.org [maintainer] and attach the "/usr/ports/devel/libtool15/work/libtool-1.5.22/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/devel/libtool15.