Re: [gentoo-user] seq24 fails to comoile

2010-10-07 Thread Arttu V.
On 10/7/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote:
 I made the changes you suggested and now got an different error ... it
 still does not compile.

It's most likely the same error. AFAICT the cause of the error is
missing in your first email. Using -j12 was probably just hiding it so
far above your snippet that it was overlooked.

As for seq24 -- there has been a bug open for a few months:

http://bugs.gentoo.org/show_bug.cgi?id=326795

I added a link to a possible upstream one-line patch in a comment in
the bug (didn't try compiling it myself).

-- 
Arttu V. -- Running Gentoo is like running with scissors



Re: [gentoo-user] seq24 fails to comoile

2010-10-07 Thread Stroller

On 7 Oct 2010, at 06:40, meino.cra...@gmx.de wrote:
 ...
 MAKEOPTS=-j 12
 
 Agh No!!!  That's probably your problem right there.
 The recommendation in the manual is N+1, where N == number of cores.  Do
 you have 11 or more cores?  I find that even that isn't always safe.  I
 set...
 
 MAKEOPTS=-j 1
 ...
 
 I made the changes you suggested and now got an different error ... it
 still does not compile. 

Did you reduce it to (the number of cores in your system + 1) or to -j 1?

If the former, try the latter.

Stroller.




Re: [gentoo-user] seq24 fails to comoile

2010-10-07 Thread meino . cramer
Stroller strol...@stellar.eclipse.co.uk [10-10-07 11:53]:
 
 On 7 Oct 2010, at 06:40, meino.cra...@gmx.de wrote:
  ...
  MAKEOPTS=-j 12
  
  Agh No!!!  That's probably your problem right there.
  The recommendation in the manual is N+1, where N == number of cores.  Do
  you have 11 or more cores?  I find that even that isn't always safe.  I
  set...
  
  MAKEOPTS=-j 1
  ...
  
  I made the changes you suggested and now got an different error ... it
  still does not compile. 
 
 Did you reduce it to (the number of cores in your system + 1) or to -j 1?
 
 If the former, try the latter.
 
 Stroller.
 

Yes, I reduces -j n to n=1 (why exist this option, if it does not
work?)

mcc




Re: [gentoo-user] seq24 fails to comoile

2010-10-07 Thread Alan McKinnon
Apparently, though unproven, at 12:01 on Thursday 07 October 2010, 
meino.cra...@gmx.de did opine thusly:

 Stroller strol...@stellar.eclipse.co.uk [10-10-07 11:53]:
  On 7 Oct 2010, at 06:40, meino.cra...@gmx.de wrote:
   ...
   
   MAKEOPTS=-j 12
   
   Agh No!!!  That's probably your problem right there.
   The recommendation in the manual is N+1, where N == number of cores. 
   Do you have 11 or more cores?  I find that even that isn't always
   safe.  I set...
   
   MAKEOPTS=-j 1
   ...
   
   I made the changes you suggested and now got an different error ... it
   still does not compile.
  
  Did you reduce it to (the number of cores in your system + 1) or to -j
  1?
  
  If the former, try the latter.
  
  Stroller.
 
 Yes, I reduces -j n to n=1 (why exist this option, if it does not
 work?)


You misunderstand. The option works just fine and does (correctly) what it is 
supposed to do.

Not all software's build systems out there plays nicely with parallel 
compiles. ooO for instance is really finicky about it.

You can't blame portage for stupid coding errors that other people make, or 
stupid configurations that you make.

 



-- 
alan dot mckinnon at gmail dot com



[gentoo-user] seq24 fails to comoile

2010-10-06 Thread meino . cramer
Hi,

 The application seq24 fails to compile on my recent Gentoo AMD64
 system.


The screen says:
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I.-pthread 
-I/usr/include/gtkmm-2.4 -I/usr/lib64/gtkmm-2.4/include 
-I/usr/include/giomm-2.4 -I/usr/lib64/giomm-2.4/include 
-I/usr/include/pangomm-1.4 -I/usr/lib64/pangomm-1.4/include 
-I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 
-I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 
-I/usr/lib64/gdkmm-2.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib64/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib64/sigc++-2.0/include -I/usr/include/cairomm-1.0 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/lib64/gtk-2.0/include 
-I/usr/include/atk-1.0 -Wall -march=amdfam10 -O2 -pipe -msse3 -MT 
seqevent.o -MD -MP -MF .deps/seqevent.Tpo -c -o seqevent.o seqevent.cpp
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I.-pthread 
-I/usr/include/gtkmm-2.4 -I/usr/lib64/gtkmm-2.4/include 
-I/usr/include/giomm-2.4 -I/usr/lib64/giomm-2.4/include 
-I/usr/include/pangomm-1.4 -I/usr/lib64/pangomm-1.4/include 
-I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 
-I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 
-I/usr/lib64/gdkmm-2.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib64/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib64/sigc++-2.0/include -I/usr/include/cairomm-1.0 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/lib64/gtk-2.0/include 
-I/usr/include/atk-1.0 -Wall -march=amdfam10 -O2 -pipe -msse3 -MT seqkeys.o 
-MD -MP -MF .deps/seqkeys.Tpo -c -o seqkeys.o seqkeys.cpp
make[2]: *** [mainwnd.o] Error 1
make[2]: *** Waiting for unfinished jobs
perform.cpp: In member function 'void perform::output_func()':
perform.cpp:1152: warning: unused variable 'jack_ticks_converted'
perform.cpp:1153: warning: unused variable 'jack_ticks_converted_last'
perform.cpp:1154: warning: unused variable 'jack_ticks_delta'
perform.cpp: In member function 'void perform::add_sequence(sequence*, int)':
perform.cpp:353: warning: array subscript is below array bounds
mv -f .deps/options.Tpo .deps/options.Po
mv -f .deps/perform.Tpo .deps/perform.Po
mv -f .deps/perftime.Tpo .deps/perftime.Po
mv -f .deps/perfnames.Tpo .deps/perfnames.Po
mv -f .deps/seqdata.Tpo .deps/seqdata.Po
mv -f .deps/seqkeys.Tpo .deps/seqkeys.Po
mv -f .deps/seqevent.Tpo .deps/seqevent.Po
mv -f .deps/perfroll.Tpo .deps/perfroll.Po
mv -f .deps/seq24.Tpo .deps/seq24.Po
mv -f .deps/perfedit.Tpo .deps/perfedit.Po
mv -f .deps/seqedit.Tpo .deps/seqedit.Po
make[2]: Leaving directory 
`/var/tmp/portage/media-sound/seq24-0.9.0/work/seq24-0.9.0/src'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/var/tmp/portage/media-sound/seq24-0.9.0/work/seq24-0.9.0/src'
make: *** [all-recursive] Error 1
 * ERROR: media-sound/seq24-0.9.0 failed:
 *   emake failed
 *
 * Call stack:
 * ebuild.sh, line   54:  Called src_compile
 *   environment, line 2312:  Called _eapi2_src_compile
 * ebuild.sh, line  646:  Called die
 * The specific snippet of code:
 *  emake || die emake failed
 *
 * If you need support, post the output of 'emerge --info 
=media-sound/seq24-0.9.0',
 * the complete build log and the output of 'emerge -pqv 
=media-sound/seq24-0.9.0'.
 * The complete build log is located at 
'/var/tmp/portage/media-sound/seq24-0.9.0/temp/build.log'.
 * The ebuild environment file is located at 
'/var/tmp/portage/media-sound/seq24-0.9.0/temp/environment'.
 * S: '/var/tmp/portage/media-sound/seq24-0.9.0/work/seq24-0.9.0'

 Failed to emerge media-sound/seq24-0.9.0, Log file:

  '/var/tmp/portage/media-sound/seq24-0.9.0/temp/build.log'



solfire:/home/mccrameremerge --info =media-sound/seq24-0.9.0
zsh: media-sound/seq24-0.9.0 not found

emerge -pqv =media-sound/seq24-0.9.0'.
 * The complete build log is located at 
'/var/tmp/portage/media-sound/seq24-0.9.0/temp/build.log'.
 * The ebuild environment file is located at 
'/var/tmp/portage/media-sound/seq24-0.9.0/temp/environment'.
 * S: '/var/tmp/portage/media-sound/seq24-0.9.0/work/seq24-0.9.0'

 Failed to emerge media-sound/seq24-0.9.0, Log file:

  '/var/tmp/portage/media-sound/seq24-0.9.0/temp/build.log'

solfire:/home/mccrameremerge -pqv =media-sound/seq24-0.9.0
[ebuild  N] media-sound/seq24-0.9.0  USE=-jack -lash
solfire:/home/mccrameremerge --info =media-sound/seq24-0.9.0
Portage 2.1.8.3 (default/linux/amd64/10.0, gcc-4.4.3, glibc-2.11.2-r0, 2.6.35.7 
x86_64)
=
System Settings
=
System uname: 
Linux-2.6.35.7-x86_64-AMD_Phenom-tm-_II_X6_1090T_Processor-with-gentoo-1.12.13
Timestamp of tree: Thu, 07 Oct 2010 01:50:01 +

Re: [gentoo-user] seq24 fails to comoile

2010-10-06 Thread Walter Dnes
On Thu, Oct 07, 2010 at 04:43:55AM +0200, meino.cra...@gmx.de wrote

 =
 System Settings
 =


 CFLAGS=-march=amdfam10 -O2 -pipe -msse3

  Let the compiler figure out the CPU.  Change that line to...
 CFLAGS=-march=native -O2 -pipe 

 CXXFLAGS=-march=amdfam10 -O2 -pipe -msse3

  The recommended way of doing things here is...

 CXXFLAGS=${CFLAGS}

...which exactly copies whatever settings you have there.
Synchronization between CFLAGS and CXXFLAGS becomes automatic this way.

 MAKEOPTS=-j 12

Agh No!!!  That's probably your problem right there.
The recommendation in the manual is N+1, where N == number of cores.  Do
you have 11 or more cores?  I find that even that isn't always safe.  I
set...

 MAKEOPTS=-j 1

and it solves quite a few problems.  Note that the final binary is just
as fast, regardless of that setting.  The compile speed is somewhat
faster with a higher number.  But you quickly lose any time savings
from that, the first time you waste several hours trying to figure out
why something isn't compiling.  MAKEOPTS=-j 1 should be mandatory.

-- 
Walter Dnes waltd...@waltdnes.org



Re: [gentoo-user] seq24 fails to comoile

2010-10-06 Thread meino . cramer
Walter Dnes waltd...@waltdnes.org [10-10-07 07:32]:
 On Thu, Oct 07, 2010 at 04:43:55AM +0200, meino.cra...@gmx.de wrote
 
  =
  System Settings
  =
 
 
  CFLAGS=-march=amdfam10 -O2 -pipe -msse3
 
   Let the compiler figure out the CPU.  Change that line to...
  CFLAGS=-march=native -O2 -pipe 
 
  CXXFLAGS=-march=amdfam10 -O2 -pipe -msse3
 
   The recommended way of doing things here is...
 
  CXXFLAGS=${CFLAGS}
 
 ...which exactly copies whatever settings you have there.
 Synchronization between CFLAGS and CXXFLAGS becomes automatic this way.
 
  MAKEOPTS=-j 12
 
 Agh No!!!  That's probably your problem right there.
 The recommendation in the manual is N+1, where N == number of cores.  Do
 you have 11 or more cores?  I find that even that isn't always safe.  I
 set...
 
  MAKEOPTS=-j 1
 
 and it solves quite a few problems.  Note that the final binary is just
 as fast, regardless of that setting.  The compile speed is somewhat
 faster with a higher number.  But you quickly lose any time savings
 from that, the first time you waste several hours trying to figure out
 why something isn't compiling.  MAKEOPTS=-j 1 should be mandatory.
 
 -- 
 Walter Dnes waltd...@waltdnes.org
 

Hi Walter,

thank you for your help,

I made the changes you suggested and now got an different error ... it
still does not compile. 

Here is the output:
x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I.-pthread 
-I/usr/include/gtkmm-2.4 -I/usr/lib64/gtkmm-2.4/include 
-I/usr/include/giomm-2.4 -I/usr/lib64/giomm-2.4/include 
-I/usr/include/pangomm-1.4 -I/usr/lib64/pangomm-1.4/include 
-I/usr/include/gtk-2.0 -I/usr/include/gtk-unix-print-2.0 
-I/usr/include/atkmm-1.6 -I/usr/include/gdkmm-2.4 
-I/usr/lib64/gdkmm-2.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib64/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib64/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib64/sigc++-2.0/include -I/usr/include/cairomm-1.0 
-I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/lib64/gtk-2.0/include 
-I/usr/include/atk-1.0 -Wall -march=native -O2 -pipe -msse3 -MT mainwnd.o 
-MD -MP -MF .deps/mainwnd.Tpo -c -o mainwnd.o mainwnd.cpp
mainwnd.cpp: In member function 'void mainwnd::file_import_dialog()':
mainwnd.cpp:531: error: invalid conversion from 'Gtk::ButtonBox*' to 
'Gtk::HButtonBox*'
make[2]: *** [mainwnd.o] Error 1

To not to pollute the mailing list again with a dozen of outputs and
logs I haven't attached those to this different posting. If you need
a certain file/log/output or whatever to fix this, please let me now!
:)

Best regards,
mcc