Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 118950 - gsf-sharp 0.6 doesn't compile
Summary: gsf-sharp 0.6 doesn't compile
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Daniel Drake (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-13 23:19 UTC by Tudor
Modified: 2006-01-20 07:59 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tudor 2006-01-13 23:19:54 UTC
checking for GTK_SHARP... yes
checking for GSF... Package libgsf-gnome-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libgsf-gnome-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgsf-gnome-1' found
configure: error: Package requirements (libgsf-1 >= 1.12.1 libgsf-gnome-1 >= 1.12.1) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively you may set the GSF_CFLAGS and GSF_LIBS environment variables
to avoid the need to call pkg-config.  See the pkg-config man page for
more details.

!!! Please attach the config.log to your bug report:
!!! /home/tudor/tmp/portage/gsf-sharp-0.6/work/gsf-sharp-0.6/config.log

!!! ERROR: dev-dotnet/gsf-sharp-0.6 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
Comment 1 Saleem Abdulrasool (RETIRED) gentoo-dev 2006-01-14 00:45:23 UTC
Please emerge libgsf before emerge gsf-sharp.  (It is in the depends so not sure why it wasnt pulled in).
Comment 2 Tudor 2006-01-14 02:37:48 UTC
Calculating dependencies ...done!
>>> emerge (1 of 2) dev-dotnet/gsf-sharp-0.6 to /
>>> md5 files   ;-) gsf-sharp-0.6.ebuild
>>> md5 files   ;-) files/digest-gsf-sharp-0.6
>>> md5 src_uri ;-) gsf-sharp-0.6.tar.gz
>>> Unpacking source...
>>> Unpacking gsf-sharp-0.6.tar.gz to /home/tudor/tmp/portage/gs
f-sharp-0.6/work
>>> Source unpacked.
 * econf: updating gsf-sharp-0.6/config.guess with /usr/share/gn
uconfig/config.guess
 * econf: updating gsf-sharp-0.6/config.sub with /usr/share/gnuc
onfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr
/share/man --infodir=/usr/share/info --datadir=/usr/share --sysc
onfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-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 i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... no
ne needed
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-li
nux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld
... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload obje
ct files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... i686-pc-linux-gnu-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 i686-pc-linux-gnu-g++... i686-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether i686-pc-linux-gnu-g++ accepts -g... yes
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g+
+ -E
checking for i686-pc-linux-gnu-g77... no
checking for i686-pc-linux-gnu-f77... no
checking for i686-pc-linux-gnu-xlf... no
checking for i686-pc-linux-gnu-frt... no
checking for i686-pc-linux-gnu-pgf77... no
checking for i686-pc-linux-gnu-fort77... no
checking for i686-pc-linux-gnu-fl32... no
checking for i686-pc-linux-gnu-af77... no
checking for i686-pc-linux-gnu-f90... no
checking for i686-pc-linux-gnu-xlf90... no
checking for i686-pc-linux-gnu-pgf90... no
checking for i686-pc-linux-gnu-epcf90... no
checking for i686-pc-linux-gnu-f95... no
checking for i686-pc-linux-gnu-fort... no
checking for i686-pc-linux-gnu-xlf95... no
checking for i686-pc-linux-gnu-ifc... no
checking for i686-pc-linux-gnu-efc... no
checking for i686-pc-linux-gnu-pgf95... no
checking for i686-pc-linux-gnu-lf95... no
checking for i686-pc-linux-gnu-gfortran... no
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 nm output from i686-pc-linux-gnu-gcc o
bject... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... no
checking for ar... ar
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking if i686-pc-linux-gnu-gcc static flag  works... yes
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-except
ions... no
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPI
C
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gcc linker (/usr/i686-pc-
linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediat
e
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 i686-pc-linux-gnu-g++... /usr/i686-pc-li
nux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld
... yes
checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-
linux-gnu/bin/ld) supports shared libraries... yes
checking for i686-pc-linux-gnu-g++ option to produce PIC... -fPI
C
checking if i686-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-g++ linker (/usr/i686-pc-
linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediat
e
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking dependency style of i686-pc-linux-gnu-g++... gcc3
checking whether to enable maintainer-specific portions of Makef
iles... no
checking for a BSD-compatible install... /bin/install -c
checking for pkg-config... /usr/bin/pkg-config
checking for i686-pc-linux-gnu-pkg-config... (cached) /usr/bin/p
kg-config
checking pkg-config is at least version 0.9.0... yes
checking for MONO_DEPENDENCY... yes
checking for mono... /usr/bin/mono
checking for mcs... /usr/bin/mcs
checking for gacutil... /usr/bin/gacutil
checking for GTK_SHARP... yes
checking for GSF... Package libgsf-gnome-1 was not found in the
pkg-config search path.
Perhaps you should add the directory containing `libgsf-gnome-1.
pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgsf-gnome-1' found
configure: error: Package requirements (libgsf-1 >= 1.12.1 libgs
f-gnome-1 >= 1.12.1) were not met.
Consider adjusting the PKG_CONFIG_PATH environment variable if y
ou
installed software in a non-standard prefix.

Alternatively you may set the GSF_CFLAGS and GSF_LIBS environmen
t variables
to avoid the need to call pkg-config.  See the pkg-config man pa
ge for
more details.

!!! Please attach the config.log to your bug report:
!!! /home/tudor/tmp/portage/gsf-sharp-0.6/work/gsf-sharp-0.6/con
fig.log

!!! ERROR: dev-dotnet/gsf-sharp-0.6 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed
!!! If you need support, post the topmost build error, NOT this                                    status message.


(In reply to comment #1)
> Please emerge libgsf before emerge gsf-sharp.  (It is in the depends so not
> sure why it wasnt pulled in).
> 

Comment 3 Peter Johanson (RETIRED) gentoo-dev 2006-01-14 23:31:11 UTC
Re-assigning to maintainer.

Tudor: compnerd asked you to emerge libgsf, *not*, emerge gsf-sharp. Can you please try emerging libgsf again? The dep is definitely there in gsf-sharp.
Comment 4 Ilya Hegai 2006-01-16 01:11:29 UTC
(In reply to comment #3)
(re-)emerging libgsf before emerging gsf-sharp doesn't help

Comment 5 Tudor 2006-01-18 05:15:34 UTC
(In reply to comment #4)
> (In reply to comment #3)
> (re-)emerging libgsf before emerging gsf-sharp doesn't help
> 

yes it doesn't help. it was the output emerging gsf-sharp AFTER emergin libgsf
Comment 6 Ilya Hegai 2006-01-18 05:24:28 UTC
(In reply to comment #5)
> yes it doesn't help. it was the output emerging gsf-sharp AFTER emergin libgsf

exactly, it was reply to asking to emerge libgsf
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2006-01-19 01:59:20 UTC
Is libgsf built with the gnome USE-flag? If not, can you see if enabling that flag makes a difference?
Comment 8 Tudor 2006-01-19 03:12:29 UTC
it worked with the "gnome" use flag for me
I deleted the epatch from the ebuild of beagle because it said "epatch not found"
how can I make it work

(In reply to comment #7)
> Is libgsf built with the gnome USE-flag? If not, can you see if enabling that
> flag makes a difference?
> 
Comment 9 Daniel Drake (RETIRED) gentoo-dev 2006-01-19 03:40:56 UTC
Reopening as we should check for the presence of that use-flag in gsf-sharp, after confirming libgsf-gnome is really needed.

The beagle ebuild does not patch anything so I don't know why you are seeing that message.
Comment 10 Daniel Drake (RETIRED) gentoo-dev 2006-01-20 07:59:00 UTC
libgsf-gnome isn't needed, I removed that check upstream and included it as a patch to gsf-sharp-0.7. Thanks for reporting. You can drop the gnome USE flag on this libgsf if you wish.