[Bug 201674] Review Request: codeblocks

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: codeblocks


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201674





------- Additional Comments From dan at danny.cz  2006-08-13 03:30 EST -------
(In reply to comment #1)
> This failed to build for me:
> 
> + chmod a+x bootstrap acinclude.m4 src/update
> + ./bootstrap
> ./bootstrap: line 43: libtoolize: command not found
> error: Bad exit status from /var/tmp/rpm-tmp.76866 (%build)
> 
> Looks like a BuildRequires: libtool is needed.

OK, BR for all autotools are needed :-)

> 
> Also, I note that the naming guidelines require that a SVN checkout be dated
> instead of using the revision number, but I'm not sure that requirement makes
> much sense.

I think that for SVN repos there should be possible to use revision number. With
CVS there is no such possibility so the dates must be used. It makes also
possible to track the official "nightly build" which use revision numbers.

> Is there a reason why you disabled parallel make?  If so, you should note that
> in the spec.  (This takes ages to build single-threaded.)

It is only an omission from some bug hunting.

> Ah, the build just failed again:
> 
> /usr/lib64/libgdk-x11-2.0.so.0: undefined reference to
> `cairo_xlib_surface_create_for_bitmap'
> /usr/lib64/libgdk-x11-2.0.so.0: undefined reference to `cairo_xlib_surface_create'
> /usr/lib64/libgdk-x11-2.0.so.0: undefined reference to
`cairo_xlib_surface_set_size'
> 
> Not sure what to do at this point.  Perhaps a missing BR: on some X or cairo
> library?

I have no idea too, all required libraries should be taken to the linker via
wxWidgets libraries. Is this from x86_64 rawhide? How much up-to-date was the
rawhide?

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.