On 1/3/06, Martin Hauser <[EMAIL PROTECTED]> wrote:
That's interesting - I am using the exact same version here, and I am not having this problem.
After doing a "make clean distclean" to be sure, I tried again now and it built fine, albeit with heaps of warnings.
For any non-GCC 4.0 users who are interested, I've put my ecore make stderr and stdout here:
http://www.geocities.jp/david_at_tokyo/e17/tmp/make_err.txt
http://www.geocities.jp/david_at_tokyo/e17/tmp/make_out.txt (sorry... euc-jp encoded, but nothing in particular to see)
Regards,
David
Hello,
i've seen several issues building ecore (lot's of spam about different visibility
of a real heap of function (all functions? )) which ended up in at the end breaking
the whole build process. I assume it was just that certain functions couldn't be
seen in the library so linking the test programm against them failed. i though managed
to build it without any errors with gcc 3.4. After browsing the source code of ecore
libs a bit, i noticed that there are some things with visibility applied, maybe those
have been gotten wrong, or the gcc 4.0 is not yet stable enough. Just to let you know,
if you'd need a full trace of the problem ( i believe the build process in this case
produces only a lot of spam, which is in my oppinion better described in those
view sentences above) let me know.
the version of the gcc that broke is
(GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)
That's interesting - I am using the exact same version here, and I am not having this problem.
After doing a "make clean distclean" to be sure, I tried again now and it built fine, albeit with heaps of warnings.
For any non-GCC 4.0 users who are interested, I've put my ecore make stderr and stdout here:
http://www.geocities.jp/david_at_tokyo/e17/tmp/make_err.txt
Regards,
David
