I just though I would share this; cd xcb-util-0.3.0 export M4=/usr/gnu/bin/m4 PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
[edward at SXCE-Workstation]:/AuroraUX/XCB/xcb-util-0.3.0:~>./configure checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/gnu/bin/mkdir -p checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for m4... /usr/gnu/bin/m4 checking for gperf... gperf 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... gcc3 checking build system type... i386-pc-solaris2.11 checking host system type... i386-pc-solaris2.11 checking for a sed that does not truncate output... /usr/bin/gsed checking for grep that handles long lines and -e... /usr/bin/ggrep checking for egrep... /usr/bin/ggrep -E checking for ld used by gcc... /usr/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking for /usr/ccs/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/xpg4/bin/nm -p checking whether ln -s works... yes checking how to recognize 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 for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 786240 checking command to parse /usr/xpg4/bin/nm -p 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... no checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... solaris2.11 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... 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/ccs/bin/ld checking if the linker (/usr/ccs/bin/ld) is GNU ld... no checking whether the g++ linker (/usr/ccs/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... no checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.11 ld.so (cached) (cached) 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 g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 static flag -static works... no checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/ccs/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... solaris2.11 ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate checking for vasprintf... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for XCB... yes checking for XCB_SHM... yes checking for XCB_RENDER... yes configure: creating ./config.status config.status: creating Makefile config.status: creating aux/Makefile config.status: creating aux/xcb-aux.pc config.status: creating reply/Makefile config.status: creating reply/xcb-reply.pc config.status: creating image/Makefile config.status: creating image/xcb-image.pc config.status: creating atom/Makefile config.status: creating atom/xcb-atom.pc config.status: creating event/Makefile config.status: creating event/xcb-event.pc config.status: creating keysyms/Makefile config.status: creating keysyms/xcb-keysyms.pc config.status: creating property/Makefile config.status: creating property/xcb-property.pc config.status: creating icccm/Makefile config.status: creating icccm/xcb-icccm.pc config.status: creating wm/Makefile config.status: creating wm/xcb-wm.pc config.status: creating renderutil/Makefile config.status: creating renderutil/xcb-renderutil.pc config.status: creating xcb_util_intro config.status: executing depfiles commands gmake check && gmake && pfexec gmake install Don't really know how useful it is, but atleat it public info/junk now :p Next step is to find out the FOX guild lines on how things should be built so I can begin testing ABI breakage. Regards, Edward. 2008/10/30 Edward O'Callaghan <victoredwardocallaghan at gmail.com>: > Martin; > In a word "what?". > Your statements are fragmented/cryptic.. really, I don't understand > what you mean some times.. > > Best Regards, > Edward. > P.S. Whats a GMAT ? > > 2008/10/30 Martin Bochnig <martin at martux.org>: >> On Thu, Oct 30, 2008 at 4:36 AM, Edward O'Callaghan >> <victoredwardocallaghan at gmail.com> wrote: >>> Martin, >>> I think you missed my point entirely. >> >> Your GMAT coach would tell you, that this is a weak statement, because >> you don't provide a single reason for your beliefs. >> But you are right, I have been confusing a few things, otherwise I >> would not have taken the time. >> I won't commit my changeset and happily return this proposal to where >> it came from. >> >> -- >> %martin bochnig >> >> >>> Alan, >>> Thanks for the more informed answer.. >>> However, what I am _try_ to ask for here is guide lines, I am prepared >>> to work on this. What CFLAGS did you want me to build with, what >>> compiler etc.. ? >>> I will look into the above cases as soon as I know the FOX 'standard >>> way of building foo' >>> Its quite involved but this could be a good project for me to get the >>> ball rolling on it.. >>> >>> Best Regards, >>> Edward. >>> >>> 2008/10/30 Alan Coopersmith <Alan.Coopersmith at sun.com>: >>>> Martin Bochnig wrote: >>>>> I just noticed, that the python versionitis (reminds me of the >>>>> auto-tools) is a problem which does not exist anymore. >>>>> I'm currently working on a Blade 100 running yesterdays new SXCE >>>>> snv_101. Don't know when exactly Python 2.5.x has been added to it, >>>>> but now it _is_ bundled: >>>> >>>> snv_99: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6555500 >>>> >>>> -- >>>> -Alan Coopersmith- alan.coopersmith at sun.com >>>> Sun Microsystems, Inc. - X Window System Engineering >>>> >>>> _______________________________________________ >>>> xwin-discuss mailing list >>>> xwin-discuss at opensolaris.org >>>> >>> >>> >>> >>> -- >>> All Documents adhered to the ISO/IEC 26300 standard file format for >>> electronic office documents, such as spreadsheets, charts, >>> presentations and word processing documents from this email address. >>> The author does not take responsibility of the recipients inability to >>> read international standards and who use proprietary products such as >>> MS Office. >>> See: http://www.openoffice.org/ >>> Edward O'Callaghan. >>> -- >>> http://fedoraproject.org/wiki/EdwardOcallaghan >>> http://moonshine.opn4.org/ >>> http://www.pcbsd.org/ >>> _______________________________________________ >>> xwin-discuss mailing list >>> xwin-discuss at opensolaris.org >>> >> > > > > -- > All Documents adhered to the ISO/IEC 26300 standard file format for > electronic office documents, such as spreadsheets, charts, > presentations and word processing documents from this email address. > The author does not take responsibility of the recipients inability to > read international standards and who use proprietary products such as > MS Office. > See: http://www.openoffice.org/ > Edward O'Callaghan. > -- > http://fedoraproject.org/wiki/EdwardOcallaghan > http://moonshine.opn4.org/ > http://www.pcbsd.org/ > -- All Documents adhered to the ISO/IEC 26300 standard file format for electronic office documents, such as spreadsheets, charts, presentations and word processing documents from this email address. The author does not take responsibility of the recipients inability to read international standards and who use proprietary products such as MS Office. See: http://www.openoffice.org/ Edward O'Callaghan. -- http://fedoraproject.org/wiki/EdwardOcallaghan http://moonshine.opn4.org/ http://www.pcbsd.org/
