GCC 4.1[beta]

Tiger683 · Posted: Wed Nov 16, 2005 6:33 pm Post subject:

Just in case someone asks why not catalyst:
i don't want previous versions of tools to get involved during the build..

_________________
Retired gentoo user

wrc1944 · Posted: Wed Nov 16, 2005 6:51 pm Post subject:

Thanks much Tiger683!

I did your fam and poppler patches manually, as I'm unsure of how to apply patches to these work files (only patched kernels before). Perhaps you could clue me in and save me time for the next time?

I saw my mistake immediately- for some reason I was trying to edit the wrong file- DNotify.c++. Stupid mistake. I'll try and do cdrdao correctly myself.

Just tried arts again- after emerging fam and poppler (thought that might have helped), and the same fno-stack-protector-all error occurs. I'll try and trace down these 3 kde failures, but I've searched/read for hours on this one, and can't come up with much so far. They did compile fine with 4.0.2

Should I replace or not use my current nxsty glibc overlay (which I used when going to 4.0.2), or leave it and also use your gcc-41-overlay too?

Hmmmmm.... Seems like I might need to use the gcc-41 overlay, and recompile the toolchain, in order to fix the 3 kde problems. Does this sound correct, or has that got nothing to do with my -fno-stack-protector errors?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Tiger683 · Posted: Wed Nov 16, 2005 7:06 pm Post subject:

Heh

My "overlay" contains only ebuilds for the packages i also provided the patches for,
so patching was unnecessary, just unpack into overlay and emerge these with -r11 as revision

as for nxsty's overlay for glibc, it's almost same as what i use currently on this system, so should be fine i think....

As for the -fno-stack-protector-all, there was a patch upstream to "fix" arts with previous versions
of gcc, might try to reverse it... well, to be honest i don't use arts (hooray for hw mixer!) , but i'll look into this

_________________
Retired gentoo user

wrc1944 · Posted: Wed Nov 16, 2005 8:31 pm Post subject:

OK- so since I already patched mine manually, I guess there's no need for your overlay.

I really dislike arts too, but I thought it was related to kdegraphics and kdenetwork not compiling. Whenever I've tried to not compile arts as the first "kde" package, i run into problems. After kde is completely installed, I always disable arts- I just seemed to need it fro the entire kde compile procedure.

New Problem: I just was forced to reboot my gcc-41 test box(local power outage), and my wireless drivers now won't load. remerged them, still no go. Modprobe doesn't work either. My gcc4.1 box is wireless only (madwifi) so I can't post from it.

I'm rebuilding the kernel right now on it, if that doesn't fix it, is it possible going from 3.4.4 to 4.0.2 (with reboots wireless still worked), but going from 4.0.2 to 4.1 (no reboots for days), then the forced reboot and no wifi, this is the problem?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Gentree · Posted: Wed Nov 16, 2005 8:36 pm Post subject:

Oh Dear!

looks like my joy and enthusiasm was a bit premature. got through mpfr gmp rebuilt binutils-2.16.91.0.4 ; source /etc/profile ;

emerge glibc...

wrc1944 · Posted: Wed Nov 16, 2005 8:59 pm Post subject:

Kernel rebuild and remerging madwifi stuff fixed my connection up- not gcc4.1 related. All I have left now is the arts, kdegraphics, and kdenetwork problems (maybe the kernel rebuild with gcc-4.1 helped that- I'll try again.
---------------------------------------------------------------

BTW, in case anyone needs it, the fix for cdrdao ( ProgressDialog:: error) is to change line 65 in /var/tmp/portage/cdrdao-1.2.0-r1/work/cdrda0-1.2.0/xdao from:

struct timeval time_;
bool ProgressDialog::time(); (THIS IS THE LINE TO CHANGE- 65)

To:

struct timeval time_;
bool time();

save the file, and run:

FEATURES="keepwork" emerge =app-cdr/cdrdao-1.2.0-r1

Thanks to Tiger683 for cluing me in on how to do this stuff!
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Tiger683 · Posted: Wed Nov 16, 2005 9:03 pm Post subject:

Strange enough, this didn't happen for cdrdao on my system.
what's the output of your emerge -avp cdrdao?

Gentree:
try swithing into the sourcedir (work/glibc-2.3.6)
and type "make"

this should raise an error.

ps: emerging binutils before glibc is rather strange, normally you would do glibc binutils gcc...
_________________
Retired gentoo user

wrc1944 · Posted: Wed Nov 16, 2005 9:10 pm Post subject:

emerge -avp cdrdao
>>> --pretend disables --ask... removing --ask from options.

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild R ] app-cdr/cdrdao-1.2.0-r1 -debug +encode +gnome -pccts 0 kB
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Gentree · Posted: Wed Nov 16, 2005 9:10 pm Post subject:

wrc1944 · Posted: Wed Nov 16, 2005 10:12 pm Post subject:

Arts failed again after kernel recompile, same error, and here's kdegraphics error I just got (again). As an example, I found the first error mentioned and would like to understand how to fix it (don't know the syntax, etc. to use related to the programming language), or if there is another problem in arts or something gcc-4.1 related causing my arts/kde problems. Any advice is appreciated- should I emerge -e system again, and retry the kde stuff?

# THE KDEGRAPHICS ERRORS:
sing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -c -o SVGNumberImpl.lo SVGNumberImpl.cc
../../ksvg/data/SVGNumberImpl.lut.h:18: error: definition of 'KSVG::SVGNumberImpl::s_hashTable' is not in namespace enclosing 'KSVG::SVGNumberImpl'
make[4]: *** [SVGNumberImpl.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
SVGHelperImpl.h: In static member function 'static void KSVG::SVGHelperImpl::applyContainer(T*, int, const QString&)':
SVGHelperImpl.h:57: error: invalid use of undefined type 'struct KSVG::SVGDocumentImpl'
../../ksvg/ecma/ksvg_scriptinterpreter.h:36: error: forward declaration of 'struct KSVG::SVGDocumentImpl'
SVGHelperImpl.h:59: error: invalid use of undefined type 'struct KSVG::SVGDocumentImpl'
../../ksvg/ecma/ksvg_scriptinterpreter.h:36: error: forward declaration of 'struct KSVG::SVGDocumentImpl'
../../ksvg/data/SVGLengthImpl.lut.h: At global scope:
../../ksvg/data/SVGLengthImpl.lut.h:25: error: definition of 'KSVG::SVGLengthImpl::s_hashTable' is not in namespace enclosing 'KSVG::SVGLengthImpl'
../../ksvg/data/SVGLengthImpl.lut.h:46: error: definition of 'KSVG::SVGLengthImplProto::s_hashTable' is not in namespace enclosing 'KSVG::SVGLengthImplProto'
../../ksvg/data/SVGLengthImpl.lut.h:85: error: definition of 'KSVG::SVGLengthImplConstructor::s_hashTable' is not in namespace enclosing 'KSVG::SVGLengthImplConstructor'
make[4]: *** [SVGLengthImpl.lo] Error 1
make[4]: Leaving directory `/var/tmp/portage/kdegraphics-3.5.0_beta2/work/kdegraphics-3.4.92/ksvg/impl'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdegraphics-3.5.0_beta2/work/kdegraphics-3.4.92/ksvg/impl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdegraphics-3.5.0_beta2/work/kdegraphics-3.4.92/ksvg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdegraphics-3.5.0_beta2/work/kdegraphics-3.4.92'
make: *** [all] Error 2

!!! ERROR: kde-base/kdegraphics-3.5.0_beta2 failed.
!!! Function kde_src_compile, Line 168, Exitcode 2
!!! died running emake, kde_src_compile:make

-----------------------------------------------------------------------------------------------------------------
# MY EXAMPLE MENTIONED ABOVE:

/var/tmp/portage/kdegraphics-3.5.0_beta2/work/kdegraphics-3.4.92/ksvg/data/SVGNumberImpl.lut.h:18: error: definition of 'KSVG::SVGNumberImpl::s_hashTable' is not in namespace enclosing 'KSVG::SVGNumberImpl'

# COMMENT BY WRC1944-
# (Lines 14-22 of SVGNumberImpl.lut.h mentioned above, 18 seems the relative line to edit):

static const struct HashEntry SVGNumberImpl__s_hashTableEntries[] = {
{ 0, 0, 0, 0, -1 },
{ 1, SVGNumberImpl::Value, DontDelete, 0, -1 }
};

const struct HashTable SVGNumberImpl::s_hashTable = { 2, 2, SVGNumberImpl__s_hashTableEntries, 2, SVGNumberImpl__s_hashTableStrings};

} // namespace
------------------------------------------------------

OR- is it possible to still use DO_NOT_COMPILE="ksvg" emerge =kde-base/kdegraphics-3.5.0_beta2

like back in previous kde days?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Tiger683 · Posted: Wed Nov 16, 2005 10:48 pm Post subject:

leave it with arts for now, a makefile has to get patched, but i'm currently patching new glibc (HEAD),
as soon as i have the stage compilation running, i will look at it....

kdegraphics: i cant do any testing now, as i use
kde svn split ebuilds, which, for the first use unsermake, and for second the dependency on
kdebase is not met, so i cant even test emerge the patched one.

T
_________________
Retired gentoo user

wrc1944 · Posted: Wed Nov 16, 2005 11:03 pm Post subject:

OK- I'll wait on arts till you can look at it.

I went ahead and tried the old:
DO_NOT_COMPILE="ksvg" emerge =kde-base/kdegraphics-3.5.0_beta2

and it compiled fine, so apparently gcc-4.1 and only ksvg are having the problems.

I've never used KSVG vectors program anyway, but I'd still like to fix it.

(I hope I mentioned before I'm not using kde split ebuilds, and am ~x86).

Thanks for all your help!

_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

wrc1944 · Posted: Wed Nov 16, 2005 11:45 pm Post subject:

Tiger683,
Couldn't resist unmasking and trying kde-base/arts-3.5.0_rc1 again (which is what I tried at first with 4.1, and it had the same error as beta2 did.

This time, it compiled perfectly with gcc-4.1_20051112, so I guess the "-fno stack-protector-all" problem is fixed in the arts rc1 version.

On this box, all that's left now is kdenetwork (I can live with the DO_NOT_COMPILE="ksvg" on kdegraphics until kde-3.5.0 final is released).

If I'm going to be doing this sort of stuff, I guess I need a basic knowledge of bash, correct? That is what these files are written in, isn't it? I'm virtually ignorant of this stuff, but I'm a quick study (even at 61 yrs.).
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Gentree · Posted: Thu Nov 17, 2005 1:11 am Post subject:

No, something around here does not like binutils -*

Just switched to the new compiler and tried emerge glibc and it dropped out just as before.

reverted binutils to 2.16.1 , now rebuilding the toolchain and on to -e system with friendly-injection.

any ideas about binutils difficulties?

TIA.

_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.

KX7-333 , AthlonXP1800+ @2.3GHz
AthlonXP-M on A7N8X @ 2.6/2.4GHz (winter/summer)
2.6.32-hh1 : portage ~x86

wrc1944 · Posted: Thu Nov 17, 2005 1:19 am Post subject:

Gentree,
I've gotten emerge -e system, and world done fine with binutils-2.16.1 (I'm pure ~x86), except for my nagging kdenetworks problem. All with friendly-injection. If you didn't have injection before, that's probably the problem.

I forgot to mention- I saw a post in this thread earlier, that implied binutils.2.16.9x..xx was newer than binutils-2.16.1. Unless I'm mistaken, that's incorrect. 2.16.1 actually is the same as 2.16.100, and the dates of the ebuilds confirm this. Easy mistake to make- .9 must be newer than .1 :wink:

Addendum:
Please anyone correct me if I'm wrong, but if we're trying to deal with unsupported cutting edge gcc versions, wouldn't it be better to run pure ~x86 systems as a basis for our experiments? Wouldn't that avoid some conflicts with older packages?
_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Tiger683 · Posted: Thu Nov 17, 2005 2:06 am Post subject:

i wouldn't worry too much about that, if you'll get headache,
then it won't be the stable package causing it

_________________
Retired gentoo user

wrc1944 · Posted: Thu Nov 17, 2005 2:24 am Post subject:

Hmmmmm... I guess I misunderstand something here, but running ~x86 for 2+ years I've had packages that did not compile (as brought in by ~x86), but then an even newer version does compile against the same gcc version (I've always kept up with the latest ~x86 gcc of course, being ~x86). Conversly, even the so-called "stable" version didn't compile on a pure ~x86 system that had before, even when I reverted to earlier gcc's??? That of course makes me think that "stable" Gentoo packages can't be expected to work in the gcc-4.1 realm.

The complexities and contradictions are apparently endless, and let's face facts- this stuff can drive even knowledgable users insane, not to mention the people like me who really don't know precisely what they're doing yet on this subject. :wink:

_________________
Main box- ASRock 880GM-LE AM3
Phenom II x6 1090T, 3.2 GHz, 8GB GSkill DDR3 1333mhz
Samsung SATA 500GB, Radeon HD 4670 1GB DDR3
Gentoo ~x86, ~amd64, glibc-2.15-r1, gcc-4.7.0, kernels 3.3.7, 3.4.0 w/auto-cgroups

Gentree · Posted: Thu Nov 17, 2005 8:21 am Post subject:

Tiger683 · Posted: Thu Nov 17, 2005 8:27 am Post subject:

Gentree, wrc :

This is not true...
2.16.9x.0.x indicates a prerelease of 2.17

T

EDIT: ok, so i managed to build something like a stage1 by hand, without any involvement
of pre4.1 compiler and pre 2.3.6 glibc

then i will probably right away use glibc-2.3.90 ebuild
with cvs snapshot from yesterday and most recent fedora tarball...
now, let's see if proceeding to stage 3 with it and using as seed for catalyst build works

emerge --sync does at least
_________________
Retired gentoo user

DaPhreak · n00b Joined: 22 Aug 2004 Posts: 13

Fuel · n00b Joined: 17 Nov 2005 Posts: 12

Tried emerging gcc-4.1.0_beta20051112

Tyler_Durden · Posted: Thu Nov 17, 2005 5:00 pm Post subject:

Gentree · Posted: Thu Nov 17, 2005 5:20 pm Post subject:

Fuel · n00b Joined: 17 Nov 2005 Posts: 12

Tiger683 · Posted: Thu Nov 17, 2005 8:48 pm Post subject:

Main comment would be, you have totally misunderstood the original purpose of
this thread, which is _testing_ to eventually discover bugs, not ricing....

The sideeffect is the "on the edge"-kick, but it can be omitted.
_________________
Retired gentoo user