public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
* could not build tksm in sid snapshot 20070801
@ 2007-08-14 10:57 suleman
  2007-08-14 11:05 ` Frank Ch. Eigler
  0 siblings, 1 reply; 6+ messages in thread
From: suleman @ 2007-08-14 10:57 UTC (permalink / raw)
  To: sid

Hi, I've successfully built sid on my ubuntu desktop but the tksm
component did not build during the configure process. In fact the
configure script didn't create a makefile in the
sid/src/sid/component/tcl folder at all.

Here is the configure command I used.

../src/configure --prefix=/opt/sid --exec-prefix=/opt/sid 2>&1 | tee
configure.out

Regards,

Suleman


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: could not build tksm in sid snapshot 20070801
  2007-08-14 10:57 could not build tksm in sid snapshot 20070801 suleman
@ 2007-08-14 11:05 ` Frank Ch. Eigler
  2007-08-16  1:51   ` suleman
  2007-08-16 13:47   ` suleman
  0 siblings, 2 replies; 6+ messages in thread
From: Frank Ch. Eigler @ 2007-08-14 11:05 UTC (permalink / raw)
  To: suleman; +Cc: sid

Hi -

> [...] the tksm component did not build during the configure
> process. In fact the configure script didn't create a makefile in
> the sid/src/sid/component/tcl folder at all.

It should have at least created a Makefile, even if tcl development
headers/libraries are absent.  You can try running the tcl-component
configure script again (a sibling of cgen-cpu/configure*) to see
what happened.

- FChE

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: could not build tksm in sid snapshot 20070801
  2007-08-14 11:05 ` Frank Ch. Eigler
@ 2007-08-16  1:51   ` suleman
  2007-08-16  2:04     ` Frank Ch. Eigler
  2007-08-16 13:47   ` suleman
  1 sibling, 1 reply; 6+ messages in thread
From: suleman @ 2007-08-16  1:51 UTC (permalink / raw)
  To: sid

> It should have at least created a Makefile, even if tcl development
> headers/libraries are absent.  You can try running the tcl-component
> configure script again (a sibling of cgen-cpu/configure*) to see
> what happened.
> 

I ran the configure again in the sid/component/tcl again. It reported it
cannot find blt.h. So I installed the blt-dev package. But still the
-tksm option is not working and it is reporting the following error.

/tmp/sid-31694.conf:50: component type sid-control-tksm unknown
/tmp/sid-31694.conf:142: component tksm not found
/tmp/sid-31694.conf:146: component tksm not found
/tmp/sid-31694.conf:157: component tksm not found
Configuration error.  Aborting.

===================================================

Here is the output of running the configure script in the
sid/component/tcl folder.

Please let me know what is missing / required for -tksm option to work

Regards

Suleman.

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 whether to enable maintainer-specific portions of Makefiles...
no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
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 ANSI C... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
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 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... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
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 static flag  works... yes
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 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... no
checking dynamic linker characteristics... sh: shopt: not found
cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
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++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... sh: shopt: not found
cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for main in -lm... yes
checking tcl in build tree... -L../../../tcl/unix -ltcl8.4
checking tk in build tree... -L../../../tk/unix -ltk8.4
checking for X... libraries /usr/lib, headers 
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for dlopen in -ldl... yes
checking for XOpenDisplay in -lX11... yes
checking blt.h usability... yes
checking blt.h presence... yes
checking for blt.h... yes
checking tcl.h usability... yes
checking tcl.h presence... yes
checking for tcl.h... yes
checking tk.h usability... yes
checking tk.h presence... yes
checking for tk.h... yes
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking for opendir... yes
checking for links... false
checking for xsltproc... true
checking for sabcmd... false
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: could not build tksm in sid snapshot 20070801
  2007-08-16  1:51   ` suleman
@ 2007-08-16  2:04     ` Frank Ch. Eigler
  0 siblings, 0 replies; 6+ messages in thread
From: Frank Ch. Eigler @ 2007-08-16  2:04 UTC (permalink / raw)
  To: suleman; +Cc: sid

Hi -

> I ran the configure again in the sid/component/tcl again. It reported it
> cannot find blt.h. So I installed the blt-dev package. 

Did this result in a plausible sidcomptcl.so file?

> But still the
> -tksm option is not working and it is reporting the following error.
> 
> /tmp/sid-31694.conf:50: component type sid-control-tksm unknown
> /tmp/sid-31694.conf:142: component tksm not found
> /tmp/sid-31694.conf:146: component tksm not found
> /tmp/sid-31694.conf:157: component tksm not found
> Configuration error.  Aborting.

This might be just an effect of not doing a "make install", without
which the tcl-bridge component would not find tksm's script.
Script-based components work by compTcl scanning for their source
files someplace in the install tree.  See the tail end of compTcl.cxx.

- FChE

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: could not build tksm in sid snapshot 20070801
  2007-08-14 11:05 ` Frank Ch. Eigler
  2007-08-16  1:51   ` suleman
@ 2007-08-16 13:47   ` suleman
  1 sibling, 0 replies; 6+ messages in thread
From: suleman @ 2007-08-16 13:47 UTC (permalink / raw)
  To: sid

Hi Frank,

>> This might be just an effect of not doing a "make install", without
>> which the tcl-bridge component would not find tksm's script.
>> Script-based components work by compTcl scanning for their source
>> files someplace in the install tree.  See the tail end of compTcl.cxx.

I cleaned the build tree completely and re-build again and performed sudo make install.

>> Did this result in a plausible sidcomptcl.so file?

I did find a libtclapi.a and libtclapi.so file in the install
path /opt/sid/sidcomp.  Is this the file? Here are more detailed
contents of the folders.

Here are the contents of the build directory sid/component/tcl

compTcl.lo  config.h    config.status  libtool   stamp-h1
compTcl.o   config.log  libtclapi.la   Makefile

and the contents of the install directory /opt/sid/lib

libbfd.a     libopcodes.a   libtclstub8.4.a  sidcomp       tk8.4
libbfd.la    libopcodes.la  libtk8.4.a       sidsamples    tkConfig.sh
libiberty.a  libtcl8.4.a    libtkstub8.4.a   tclConfig.sh

and the contents of the install directory /opt/sid/lib/sidcomp

libaudio.a            libide.la                     libparport.so.0.0.0
libaudio.la           libide.so                     libprof.a
libaudio.so           libide.so.0                   libprof.la
libaudio.so.0         libide.so.0.0.0               libprof.so
libaudio.so.0.0.0     libinterrupt.a                libprof.so.0
libcache.a            libinterrupt.la               libprof.so.0.0.0
libcache.la           libinterrupt.so               librtc.a
libcache.so           libinterrupt.so.0             librtc.la
libcache.so.0         libinterrupt.so.0.0.0         librtc.so
libcache.so.0.0.0     liblcd-char-display.a         librtc.so.0
libcgencpu.a          liblcd-char-display.la        librtc.so.0.0.0
libcgencpu.la         liblcd-char-display.so        libsched.a
libcgencpu.so         liblcd-char-display.so.0      libsched.la
libcgencpu.so.0       liblcd-char-display.so.0.0.0  libsched.so
libcgencpu.so.0.0.0   libloader.a                   libsched.so.0
libconfig.a           libloader.la                  libsched.so.0.0.0
libconfig.la          libloader.so                  libt6963c.a
libconsoles.a         libloader.so.0                libt6963c.la
libconsoles.la        libloader.so.0.0.0            libt6963c.so
libconsoles.so        libmapper.a                   libt6963c.so.0
libconsoles.so.0      libmapper.la                  libt6963c.so.0.0.0
libconsoles.so.0.0.0  libmapper.so                  libtclapi.a
libgdb.a              libmapper.so.0                libtclapi.la
libgdb.la             libmapper.so.0.0.0            libtclapi.so
libgdb.so             libmemory.a                   libtclapi.so.0
libgdb.so.0           libmemory.la                  libtclapi.so.0.0.0
libgdb.so.0.0.0       libmemory.so                  libtimers.a
libgloss.a            libmemory.so.0                libtimers.la
libgloss.la           libmemory.so.0.0.0            libtimers.so
libgloss.so           libmepfamily.a                libtimers.so.0
libgloss.so.0         libmepfamily.la               libtimers.so.0.0.0
libgloss.so.0.0.0     libmepfamily.so               libuart.a
libglue.a             libmepfamily.so.0             libuart.la
libglue.la            libmepfamily.so.0.0.0         libuart.so
libglue.so            libmmu.a                      libuart.so.0
libglue.so.0          libmmu.la                     libuart.so.0.0.0
libglue.so.0.0.0      libmmu.so                     libx86.a
libhd44780u.a         libmmu.so.0                   libx86.la
libhd44780u.la        libmmu.so.0.0.0               libx86.so
libhd44780u.so        libparport.a                  libx86.so.0
libhd44780u.so.0      libparport.la                 libx86.so.0.0.0
libhd44780u.so.0.0.0  libparport.so
libide.a              libparport.so.0

Best Regards

Suleman


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: could not build tksm in sid snapshot 20070801
@ 2007-08-15 13:06 suleman
  0 siblings, 0 replies; 6+ messages in thread
From: suleman @ 2007-08-15 13:06 UTC (permalink / raw)
  To: sid

>> It should have at least created a Makefile, even if tcl development
>> headers/libraries are absent.  You can try running the tcl-component
>> configure script again (a sibling of cgen-cpu/configure*) to see
>> what happened.

Sorry, I was looking in the source tree for makefile. It was there in the build tree.

Could it be that since the first time I ran configure script, there were no development files for tcl/tk.
Later I installed the tcl/tk dev files and ran the configure script again. But it still did not generate the proper commands in the makefile to build the tksm component.

Suleman

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2007-08-16 13:47 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-08-14 10:57 could not build tksm in sid snapshot 20070801 suleman
2007-08-14 11:05 ` Frank Ch. Eigler
2007-08-16  1:51   ` suleman
2007-08-16  2:04     ` Frank Ch. Eigler
2007-08-16 13:47   ` suleman
2007-08-15 13:06 suleman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).