Bugzilla Bug 51589

When emerging app-cdr/cdrdao-1.1.8-r1 -debug +gnome, gcdmaster won't compile.

According to LSD` on freenode #gentoo this is due to the following:

"linfan: it can be fixed, all they need to do is set specific deps on the cdrdao ebuild and correct the slotting on two of the packages but its probably easier to do it manually (copying the two packages that need slot adjustment to an overlay to avoid emerge sync nuking them)"

He said it was due to gtkmm and libgnomeuimm

I can understand what he had in mind, but I am not skilled enough to fix it myself as I do not understand what is meant by slotting.

Hope this can be of any use.

As I try to start Gnome CD Master from the Application:Other i get an error box saying: Cannot launch entry\ Details: Failed to execute child process\ "gcdmaster" (No such file or directory)

Regards,

Borje

Created an attachment (id=31936) [details]
Move gcdmaster to sigc++-2.0,  gtkmm-2.4, and  libgnomeuimm-2.6

This patch is against the vanilla cdrdao-1.1.8 and makes gcdmaster compile with
the new interfaces provided by sigc++-2.0, gtkmm-2.4, and libgnomeuimm-2.6.

To get the port compile I had to disable the AudioCDView::drag_data_received_cb

callback (but appearently it didn't do anything yet), and the
AutoCDProject::Toolbar2() method which is also not used (as far as I can see).

The patch has already been submitted to the cdrdao project:
http://sourceforge.net/tracker/index.php?func=detail&aid=958557&group_id=2171&atid=302171

khai this is yours fix. Like all *mm packages like i said. You should've really
done this by now.

Created an attachment (id=32037) [details]
cdrdao-1.1.8-r1.ebuild

This should help the poster until changes are made in the tree

This is what happened when emerging cdrdao-1.1.8-r1.ebuild:

emerge cdrdao
Calculating dependencies ...done!
>>> emerge (1 of 2) dev-cpp/libgnomeuimm-2.0.0 to /
>>> Downloading http://ds.thn.htu.se/linux/gentoo/distfiles/libgnomeuimm-2.0.0.tar.gz
--02:19:21--  http://ds.thn.htu.se/linux/gentoo/distfiles/libgnomeuimm-2.0.0.tar.gz
           => `/usr/portage/distfiles/libgnomeuimm-2.0.0.tar.gz'
Resolving ds.thn.htu.se... 193.10.192.105
Connecting to ds.thn.htu.se[193.10.192.105]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 429,018 [application/x-gzip]
 
100%[====================================>] 429,018      180.18K/s
 
02:19:23 (179.74 KB/s) - `/usr/portage/distfiles/libgnomeuimm-2.0.0.tar.gz' saved [429018/429018]
 
>>> md5 src_uri ;-) libgnomeuimm-2.0.0.tar.gz
>>> Unpacking source...
>>> Unpacking libgnomeuimm-2.0.0.tar.gz to /var/tmp/portage/libgnomeuimm-2.0.0/work
 * Applying libgnomeuimm-2.0.0-gcc2_fix.patch...                          [ ok ]>>> Source unpacked.
 * Patching ${S}/scripts/ltmain.sh...
 *   Applying portage-1.4.1.patch...
 *   Applying max_cmd_len-1.5.0.patch...
 *   Applying tmp-1.3.5.patch...
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
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 i686-pc-linux-gnu-strip... no
checking for strip... strip
checking whether to enable maintainer-specific portions of Makefiles... no
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output... 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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking whether make sets $(MAKE)... (cached) yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i686-pc-linux-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 object files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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++... 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 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-fl32... no
checking for i686-pc-linux-gnu-af77... no
checking for i686-pc-linux-gnu-fort77... 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-lf95... no
checking for i686-pc-linux-gnu-g95... no
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... 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 lf95... no
checking for g95... 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 gcc object... 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... 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/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/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/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
appending configuration tag "F77" to libtool
checking for gm4... no
checking for m4... m4
checking whether m4 is GNU m4... yes
checking whether make is GNU Make... yes
checking for pkg-config... /usr/bin/pkg-config
checking for libgnomeui-2.0 >= 1.111.1 libgnomemm-2.0 >= 1.3.10 libgnomecanvasmm-2.0 >= 2.0.0 gconfmm-2.0 >= 2.0.1 libglademm-2.0 >= 2.0.0... Package libgnomemm-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libgnomemm-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libgnomemm-2.0' found
 
configure: error: Library requirements (libgnomeui-2.0 >= 1.111.1 libgnomemm-2.0 >= 1.3.10 libgnomecanvasmm-2.0 >= 2.0.0 gconfmm-2.0 >= 2.0.1 libglademm-2.0 >= 2.0.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.
 
!!! ERROR: dev-cpp/libgnomeuimm-2.0.0 failed.
!!! Function econf, Line 365, Exitcode 1
!!! econf failed

sorry, wasn't aware the the old mm ebuilds had not been updated. change the
libgnomeuimm ebuild to dep on that specific version of libgnomemm(replace the
>= with =). You may run into similar problems with other older packages, if so,
use this example to work around them.

Changed the libgnomeuimm to =2.6.0

Same result as from start. Doesn't launch - apparently did not compile.

I didn't say to change the version to 2.6.0, keep the versions at what they
are. You can also do emerge =dev-cpp/libgnomeuimm-2.0.0 and the same for the
proper versions of other mm libs.

Understand nada. 

Please tell me in English, what I should do. And, if possible, step by step. And you are welcome to get mad at me, I can take it :-)

Any way, I recently figured out how cdrecord works and have configured an other acceptable burner gui, so I reckon I don't need gcdmaster.

Thank you for trying.

Have a nice day.

Ah, but you see, just because you don't need it does not mean that others
don't. So, with that, please let me know what I can do to help close this bug.

The problem seems to be in the rdepend part of the ebuild. With some help from
the cdrdao folks, I found out that I needed both gtkmm 2.2.x and  gconfmm-2.0.x
for this to emerge successfully. Newer and older versions of these libraries
won't do it, although the cdrdao in cvs apparently will work with the newest
library versions.

Stephen

Thanx.

I have done two reinstalls since I started this bug - and now gcdmaster compiles and seems to work. So, as for me, you can close this bug.

I won't use gcdmaster, though. I'll just stick to cdrecord from command line.

As a matter of fact, I don't like gnome at all for the moment - it gives me ulcers, it is slow and shaky and seems to be in some kind of heavy don't-know-what development stage. But, as usual, there is no info of what's going on in the background, and probably nobody knows. That's just plain reality that I will have to accept.

borje

khai, those deps should've been fixed by now really..

reassigning to maintainer.. the *mm deps need to be =<version>*'ed ..

The dependencies are now fixed for cdrdao-1.1.8-r1.  It's still in portage
testing, so please try it.

*** Bug 56661 has been marked as a duplicate of this bug. ***

Although there is now cdrdao-1.1.9 in portage, we still have problems with bug
49372 and the gnome-use-flag.  Adding dependency to this bug.

cdrdao-1.1.9 compiles fine on GCC-3.4.1 and and GLIBC-2.3.4.20040619  with
+Gnome use flag if you're running the latest Gnome packages (ver-2.7.x) from
breakmygentoo. I just had to remove the version numbers from the build rdepend
refering to gnome apps and edit out the warning about not building with the
Gnome flag then placed my edited ebuild in my portage overlay and all worked
fine. I've burned a couple of disks already today since I rebuilt it this
afternoon. I hope this helps someone, ciao.

*** Bug 59345 has been marked as a duplicate of this bug. ***

*** Bug 59351 has been marked as a duplicate of this bug. ***

Created an attachment (id=38814) [details]
-gnome gcc 3.4.1 compile fix

This is addressed to http://bugs.gentoo.org/show_bug.cgi?id=56661 (a duplicate
of this bug).It will make it compile although I don't use cdrdao so I don't
know if it works.It has to be copied into files under the ebuild's source tree
and modify the	ebuild accordingly obviously

It seems that all dependencies of cdrdao-1.1.9 are resolved now.  On my systems
cdrdao compiles fine with gcdmaster.

If I can get some more positive feedback for cdrdao-1.1.9, I can commit it into
stable.

[ebuild  N    ] dev-cpp/libglademm-2.2.0  -debug 0 kB

This won't build right now.  1.1.9 does therefore not work on amd64.

Does anybody know, what's the deal with gcdmaster? It does not offer the most
important menus mentioned in the man page. That is the "Tools" Menu, which
allows inserting audio files and some entries below the "Edit" menu, for
setting, editing and removing track marks.

My menu toolbar contains

File | Edit | Actions | Settings | Info

and when starting gcdmaster from shell, I see

(gcdmaster:1052): GnomeUI-WARNING **: gnome_app_insert_menus_custom: couldn't
find insertion point for menus!

(gcdmaster:1052): GnomeUI-WARNING **: gnome_app_insert_menus_custom: couldn't
find insertion point for menus!

Could it be that due to the errors above the most important menus are missing /
incomplete, leaving gcdmaster totally useless?

probably, but put it in another bug.

changing deps because bugzilla is dumb and doesn't do it when a dep is marked
as a dupe.  will file this as a bugzilla bug.

Now that that dep is resolved, the remaining bug is, as stated in the ebuild, a
gcc 3.4 issue.  You may therefore want to reassign this bug to gcc-porting@
(iirc that's correct).

for what it's worth i happened to fix this the other day 1.1.8-r1 and 1.1.9 are
compiling and appear to be working gcdmaster id well

More specifically, Daniel fixed the gcc 3.4 issues, not necessarily any other
outstanding issues.