LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-24-2005, 04:41 PM   #1
brokenflea
Member
 
Registered: Nov 2003
Distribution: Slackware 11.0, FreeBSD
Posts: 284

Rep: Reputation: 30
F-Spot


i'm trying to run F-Spot on my notebook running gnome 2.10
everytime i do ./configure it fails and this is what it brings up:
Code:
checking for mono.pc... configure: error: missing the mono.pc file, usually found in the mono-devel package
and i did install the mono package from http://www.mono-project.com and it installed under /opt.
do i need to do something different at this point.
any advice would be greatly appreciated.

TIA
 
Old 06-24-2005, 05:59 PM   #2
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
try ./configure --help
There could be an option to specify the mono installation directory
 
Old 06-24-2005, 06:09 PM   #3
brokenflea
Member
 
Registered: Nov 2003
Distribution: Slackware 11.0, FreeBSD
Posts: 284

Original Poster
Rep: Reputation: 30
this is what it brings up when i type in ./configure --help
Code:
./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version           display version information and exit
  -q, --quiet, --silent   do not print `checking...' messages
      --cache-file=FILE   cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create         do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR           user executables [EPREFIX/bin]
  --sbindir=DIR          system admin executables [EPREFIX/sbin]
  --libexecdir=DIR       program executables [EPREFIX/libexec]
  --datadir=DIR          read-only architecture-independent data [PREFIX/share]
  --sysconfdir=DIR       read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR   modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  --libdir=DIR           object code libraries [EPREFIX/lib]
  --includedir=DIR       C header files [PREFIX/include]
  --oldincludedir=DIR    C header files for non-gcc [/usr/include]
  --infodir=DIR          info documentation [PREFIX/info]
  --mandir=DIR           man documentation [PREFIX/man]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Optional Features:
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --enable-maintainer-mode  enable make rules and dependencies not useful
                          (and sometimes confusing) to the casual installer
  --disable-dependency-tracking  speeds up one-time build
  --enable-dependency-tracking   do not reject slow dependency extractors
  --enable-shared[=PKGS]
                          build shared libraries [default=yes]
  --enable-static[=PKGS]
                          build static libraries [default=yes]
  --enable-fast-install[=PKGS]
                          optimize for fast installation [default=yes]
  --disable-libtool-lock  avoid locking (might break parallel builds)
  --disable-glibtest      do not try to compile and run a test GLIB program
  --disable-schemas-install     Disable the schemas installation

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
  --with-pic              try to use only PIC/non-PIC objects [default=use
                          both]
  --with-tags[=TAGS]
                          include additional configurations [automatic]
  --with-gconf-source=sourceaddress      Config database for installing schema files.
  --with-gconf-schema-file-dir=dir        Directory for installing schema files.

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  CPPFLAGS    C/C++ preprocessor flags, e.g. -I<include dir> if you have
              headers in a nonstandard directory <include dir>
  CPP         C preprocessor
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags
  CXXCPP      C++ preprocessor
  F77         Fortran 77 compiler command
  FFLAGS      Fortran 77 compiler flags

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
i did try to do ./configure --with-mono=/opt/mono-1.1.8.1 , but still no luck, still gives me that same error
 
Old 06-24-2005, 06:48 PM   #4
ralvez
Member
 
Registered: Oct 2003
Location: Canada
Distribution: ArchLinux && Slackware 10.1
Posts: 298

Rep: Reputation: 30
Since you are running Slack you can use slocate to make sure that you indeed have the "mono.pc." file in your system.
Issue (at the prompt) the following command: slocate mono.pc
If you get a warning like: "slocate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old" issue this command "updatedb" and then "slocate mono.pc"
Hope this helps

Rick

Last edited by ralvez; 06-24-2005 at 06:51 PM.
 
Old 06-24-2005, 08:58 PM   #5
brokenflea
Member
 
Registered: Nov 2003
Distribution: Slackware 11.0, FreeBSD
Posts: 284

Original Poster
Rep: Reputation: 30
thanks for the info Rick. i ran slocate mono.pc initially and it brought up the same error message
Code:
warning: slocate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old
so, i ran updatedb and then ran slocate mono.pc again and it brought up:

Code:
/opt/mono-1.1.8.1/lib/pkgconfig/mono.pc
so now i know that its there, how do i have ./configure recognize it.
thanks for all your help
 
Old 06-24-2005, 09:13 PM   #6
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 14.1
Posts: 1,138

Rep: Reputation: 55
you can do this,

$ PKG_CONFIG_PATH=/opt/mono-1.1.8.1/lib/pkgconfig/mono.pc
$ export PKG_CONFIG_PATH

and then run regular ./configure

Tux,
 
Old 06-24-2005, 10:35 PM   #7
brokenflea
Member
 
Registered: Nov 2003
Distribution: Slackware 11.0, FreeBSD
Posts: 284

Original Poster
Rep: Reputation: 30
that worked, thanks for your input, now i'm stuck with another problem while doing ,/configure, here's the error:

Code:
checking for sqlite_last_insert_rowid in -lsqlite... no
configure: error: sqlite not found
so i downloaded the sqlite source from sqlite.org and installed it and that went fine and at the end of make install it gave this output:

Code:
/usr/bin/ginstall -c -d /usr/local/bin
./libtool --mode=install /usr/bin/ginstall -c sqlite3 /usr/local/bin
/usr/bin/ginstall -c .libs/sqlite3 /usr/local/bin/sqlite3
/usr/bin/ginstall -c -d /usr/local/include
/usr/bin/ginstall -c -m 0644 sqlite3.h /usr/local/include
/usr/bin/ginstall -c -d /usr/local/lib/pkgconfig;
/usr/bin/ginstall -c -m 0644 sqlite3.pc /usr/local/lib/pkgconfig;
how do i fix this now. thanks in advance.
 
Old 06-24-2005, 10:56 PM   #8
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 14.1
Posts: 1,138

Rep: Reputation: 55
I'm sorry, I didn't get your question. Did your sqlite installation go well?

If you sqlite installation went well, then basically you can run ./configure again and see if you are lucky. Frankly F-spot has lot of deps that need to be installed. I actually installed f-spot but didn't find it worthwhile so i just use gthumb that comes with gnome.

Tux,
 
Old 06-24-2005, 11:04 PM   #9
brokenflea
Member
 
Registered: Nov 2003
Distribution: Slackware 11.0, FreeBSD
Posts: 284

Original Poster
Rep: Reputation: 30
i'm sorry if i confused you. the sqlite installation went perfectly fine, no problem whatsoever. so i did ./configure with f-spot and no go on that. i think i'm gonna give it a break tonight and work on it tomorrow. you're right, i do have gthumb to work with as far as the camera goes. thanks for all your help. you're awesome.
 
Old 08-05-2005, 05:42 PM   #10
mictlan
LQ Newbie
 
Registered: Dec 2004
Posts: 2

Rep: Reputation: 0
this is the solution...

Well you need to do this (sorry my bad english...)

* Download SQlite Library (some like this sqlite-2.8.16.so.gz A precompiled shared-library for Linux. This is the same as tclsqlite.so.gz but without the TCL bindings.)
* Unzip (gzip -d sqlite.XXX.gz)
* Copy to /usr/lib how libsqlite.so -need be root- (cp sqlite-XXX /usr/lib/libsqlite.so)
* Run ldconfig for update libraries (ldconfig)

Then f-spot works...
 
Old 12-29-2005, 04:02 PM   #11
pxumsgdxpcvjm
Member
 
Registered: Aug 2005
Posts: 235

Rep: Reputation: 30
Quote:
Originally Posted by tuxrules
you can do this,

$ PKG_CONFIG_PATH=/opt/mono-1.1.8.1/lib/pkgconfig/mono.pc
$ export PKG_CONFIG_PATH

and then run regular ./configure

Tux,
I've been having the same trouble but this didn't work for me. Still getting the same error message. I used "locate" to find mono.pc

Seems to see some of mono:
checking for mono... /opt/mono-1.1.12.1/bin/mono
checking for mcs... /opt/mono-1.1.12.1/bin/mcs
checking for mono.pc... configure: error: missing the mono.pc file, usually found in the mono-devel package

Thanks for any help.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
F-spot for fc4 Sharktale Fedora 1 02-20-2006 01:49 AM
f-spot dates viniosity Linux - Software 1 08-07-2005 07:43 PM
f-spot picture software joshcav Linux - Software 1 06-08-2005 06:07 AM
How to Spot a Motherboard gone bad. New2Lindows General 3 08-17-2003 08:46 PM
Wi-Fi Hot Spot software greenranger Linux - Networking 0 03-17-2003 10:32 AM


All times are GMT -5. The time now is 04:30 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration