[PC-BSD Testing] libX11 config failure

Kris Moore kris at pcbsd.com
Thu Mar 26 08:23:30 PST 2009


Larry Gadallah wrote:
> Hi Kris:
> 
> 2009/3/25 <testing-request at lists.pcbsd.org>
> 
>>> I tried the following this morning:
>>>
>>> # remove ports tree
>>> mv /usr/ports /usr/ports.old
>>> # get current ports tree
>>> portsnap fetch
>>> portsnap extract
>>> # delete existing installed packages
>>> pkg_delete --all
>>> # try building libX11 again
>>> cd /usr/ports/x11/libX11
>>> make
>>>
>>> I get these (different) results on the second and later attempts to make:
>>>
>>> larry at pinawa% sudo make
>>> Password:
>>> ===>   libX11-1.2,1 depends on file: /usr/local/libdata/pkgconfig/xcb.pc
>> -
>>> found
>>> ===>   libX11-1.2,1 depends on file:
>> /usr/local/share/aclocal/xorg-macros.m4
>>> - found
>>> ===>   libX11-1.2,1 depends on file:
>>> /usr/local/libdata/pkgconfig/bigreqsproto.pc - found
>>> ===>   libX11-1.2,1 depends on file:
>>> /usr/local/libdata/pkgconfig/xcmiscproto.pc - found
>>> ===>   libX11-1.2,1 depends on file:
>>> /usr/local/libdata/pkgconfig/xextproto.pc - found
>>> ===>   libX11-1.2,1 depends on file:
>> /usr/local/libdata/pkgconfig/xtrans.pc
>>> - found
>>> ===>   libX11-1.2,1 depends on file:
>> /usr/local/libdata/pkgconfig/kbproto.pc
>>> - found
>>> ===>   libX11-1.2,1 depends on file:
>>> /usr/local/libdata/pkgconfig/inputproto.pc - found
>>> ===>   libX11-1.2,1 depends on file:
>>> /usr/local/libdata/pkgconfig/xf86bigfontproto.pc - found
>>> ===>   libX11-1.2,1 depends on file: /usr/local/libdata/pkgconfig/xau.pc
>> -
>>> found
>>> ===>   libX11-1.2,1 depends on file:
>> /usr/local/libdata/pkgconfig/xdmcp.pc -
>>> found
>>> ===>   libX11-1.2,1 depends on file:
>> /usr/local/libdata/pkgconfig/xproto.pc
>>> - found
>>> ===>   libX11-1.2,1 depends on file: /usr/local/bin/automake-1.10 - not
>>> found
>>> ===>    Verifying install for /usr/local/bin/automake-1.10 in
>>> /usr/ports/devel/automake110
>>> ===>   automake-1.10.1 depends on file: /usr/local/bin/perl5.8.9 - found
>>> ===>   automake-1.10.1 depends on file: /usr/local/bin/autoconf-2.62 -
>> not
>>> found
>>> ===>    Verifying install for /usr/local/bin/autoconf-2.62 in
>>> /usr/ports/devel/autoconf262
>>> ===>  Installing for autoconf-2.62
>>> ===>   autoconf-2.62 depends on executable: gm4 - found
>>> ===>   autoconf-2.62 depends on executable: autoconf-wrapper - found
>>> ===>   autoconf-2.62 depends on file: /usr/local/bin/perl5.8.9 - found
>>> ===>   Generating temporary packing list
>>> ===>  Checking if devel/autoconf262 already installed
>>> gmake  install-recursive
>>> gmake[1]: Entering directory
>>> `/usr/ports/devel/autoconf262/work/autoconf-2.62'
>>> Making install in bin
>>> gmake[2]: Entering directory
>>> `/usr/ports/devel/autoconf262/work/autoconf-2.62/bin'
>>> autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg'
>>> ../bin/autom4te -B '..'/lib -B '..'/lib         --language M4sh --cache
>> ''
>>> --melt ./autoconf.as -o autoconf.in
>>> autom4te: need GNU m4 1.4 or later: /usr/local/bin/gm4
>>> gmake[2]: *** [autoconf.in] Error 1
>>> gmake[2]: Leaving directory
>>> `/usr/ports/devel/autoconf262/work/autoconf-2.62/bin'
>>> gmake[1]: *** [install-recursive] Error 1
>>> gmake[1]: Leaving directory
>>> `/usr/ports/devel/autoconf262/work/autoconf-2.62'
>>> gmake: *** [install] Error 2
>>> *** Error code 2
>>>
>>> Stop in /usr/ports/devel/autoconf262.
>>> *** Error code 1
>>>
>>> Stop in /usr/ports/devel/automake110.
>>> *** Error code 1
>>>
>>> Stop in /usr/ports/x11/libX11.
>>>
>>> This leads to an important question: What is the prescribed way to
>> install
>>> and build ports for PC-BSD? Should portsnap be used, or cvsup, or ??
>>>
>>> Cheers,
>>>
>>>
>> Take a look here:
>>
>> autom4te: need GNU m4 1.4 or later: /usr/local/bin/gm4
>>
>> Looks like the version of m4 installed is too old for some reason. Maybe
>> it just got updated in ports, try to rebuild devel/m4 first.
>>
>> As for the prescribed way, you can use portsnap or cvs, they both get
>> you to the same ports tree in the end :)
>>
>> Just to re-confirm, you are using the "runports" command before you try
>> to do the builds right?
>>
>> http://wiki.pcbsd.org/index.php/Working_with_FreeBSD_Ports
>>
> 
> I think you can write this off to an RTFM error: After running
> "/PCBSD/Scripts/runports.sh" my builds work fine.
> 
> Cheers,
> 

Glad that fixed it :)

--
Kris Moore
PC-BSD Software
http://www.pcbsd.com


More information about the Testing mailing list