From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] seq24 fails to comoile
Date: Thu, 7 Oct 2010 07:40:05 +0200 [thread overview]
Message-ID: <20101007054005.GA20206@solfire> (raw)
In-Reply-To: <20101007052740.GB17511@waltdnes.org>
Walter Dnes <waltdnes@waltdnes.org> [10-10-07 07:32]:
> On Thu, Oct 07, 2010 at 04:43:55AM +0200, meino.cramer@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"
>
> Arrrrrrrrgh Nooooooooo!!! 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 <waltdnes@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
next prev parent reply other threads:[~2010-10-07 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 2:43 [gentoo-user] seq24 fails to comoile meino.cramer
2010-10-07 5:27 ` Walter Dnes
2010-10-07 5:40 ` meino.cramer [this message]
2010-10-07 8:38 ` Arttu V.
2010-10-07 9:15 ` Stroller
2010-10-07 10:01 ` meino.cramer
2010-10-07 11:26 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101007054005.GA20206@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox