Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./configure issue: Glib #1420

Closed
mc-butler opened this issue Jul 22, 2009 · 15 comments
Closed

./configure issue: Glib #1420

mc-butler opened this issue Jul 22, 2009 · 15 comments
Assignees
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/1420
Reporter zaytsev (@zyv)

Hi!

I'm trying to get RHEL4 mc builds rolling. RHEL4 a widely deployed server distro which recently got updated to 4.7, so it is one of the important targets for mc/ssh. Basically the buildlog is here:

http://nopaste.com/p/aW0XbKvEV

Now check this out:

checking for GLIB... Requested 'glib-2.0 >= 2.6' but version of GLib is 2.4.7
no

The GLib version shipped with RHEL4.7 is in fact glib2-2.4.7-1.i386.rpm , but instead of aborting at glib-2.0 >= 2.6 the ./configure process goes on.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jul 25, 2009 at 17:44 UTC (comment 1)

I will address the EL4 issue in a separate ticket.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Jul 25, 2009 at 17:44 UTC (comment 2)

  • Description edited

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Aug 1, 2009 at 16:02 UTC (comment 3)

  • Summary changed from Glib ./configure issue to ./configure issue: Glib

@mc-butler
Copy link
Author

Changed by angel_il (@ilia-maslakov) on Aug 12, 2009 at 21:22 UTC (comment 4)

  • Milestone changed from 4.7.0-pre2 to 4.7.0-pre3

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 18, 2009 at 12:52 UTC (comment 5)

  • Owner set to slavazanko
  • Severity changed from no branch to on review
  • Status changed from new to accepted

created branch 1420_configure_issue_glib (parent: master)

Initial [aece330708a522ef0703f497b3f549583b513f4b]

review, please.

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Sep 18, 2009 at 12:56 UTC (comment 6)

Maybe old/incompatible, but not bad? Glib can't be bad ;-)

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 18, 2009 at 14:04 UTC (comment 7)

"glib-2.0 not found or version too old"

right?

@mc-butler
Copy link
Author

Changed by zaytsev (@zyv) on Sep 18, 2009 at 14:08 UTC (comment 8)

Sounds good to me!

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 18, 2009 at 14:14 UTC (comment 9)

review [7181f8b6bb97a67e9ce012c0608b6921c3439ac7]

BTW, you may vote fot this branch (you ticketstarter).

Check if bug is avoid before :)

@mc-butler
Copy link
Author

Changed by iNode (@iNode) on Sep 20, 2009 at 15:44 UTC (comment 10)

It's not descriptive error message isn't error should report minimal required version of libglib-2?

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 22, 2009 at 8:07 UTC (comment 11)

Added minimal version number into error output.

[b0013c8a828364cd1d50f869328fde07434f42c2]

review

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Sep 22, 2009 at 8:20 UTC (comment 12)

  • Votes set to andrew_b

@mc-butler
Copy link
Author

Changed by angel_il (@ilia-maslakov) on Sep 22, 2009 at 8:28 UTC (comment 13)

  • Severity changed from on review to approved
  • Votes changed from andrew_b to andrew_b angel_il

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 22, 2009 at 8:48 UTC (comment 14)

  • Resolution set to fixed
  • Status changed from accepted to testing

merge [ef5434f]

@mc-butler
Copy link
Author

Changed by slavazanko (@slavaz) on Sep 22, 2009 at 8:49 UTC (comment 15)

  • Status changed from testing to closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress
Development

No branches or pull requests

2 participants