Bug 283538 – net-misc/modemmanager-0.2_p20090824 fails to compile

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Gene Imes 2009-09-02 17:22:46 UTC]

modemmanager fails to emerge

Reproducible: Always

Steps to Reproduce:
1.emerge modemmanager
2.
3.

Actual Results:  
cc1: warnings being treated as errors
mm-plugin-base.c: In function ‘supports_port’:
mm-plugin-base.c:669: warning: ‘ret’ may be used uninitialized in this function
mm-plugin-base.c:669: note: ‘ret’ was declared here
make[3]: *** [modem_manager-mm-plugin-base.o] Error 1



Can supply any other info I have.

Thanks,

Gene

[Comment 1 Rémi Cardona (RETIRED) 2009-09-02 17:33:16 UTC]

Please don't select the GNOME component if the package isn't owned by the Gnome herd. Use "Applications" or "Ebuilds" instead.

Thanks

[Comment 2 Romain Perier (RETIRED) 2009-09-02 19:35:18 UTC]

And please give a full build.log too

[Comment 3 Robert Piasek (RETIRED) 2009-09-12 20:29:12 UTC]

Hi,

Could you please provide emerge --info and full build log?

Thanks

[Comment 4 Gene Imes 2009-09-15 16:08:17 UTC]

Created attachment 204213 [details]
ebuild log

[Comment 5 Gene Imes 2009-09-15 16:09:23 UTC]

Created attachment 204215 [details]
emerge info

[Comment 6 Gene Imes 2009-09-23 14:24:31 UTC]

(In reply to comment #5)
> Created an attachment (id=204215) [edit]
> emerge info
> 

Any progress?

Thanks,

Gene

[Comment 7 Robert Piasek (RETIRED) 2009-09-23 18:44:04 UTC]

I'm going to do a revision bump in the next couple of days.
Could you please try compiling it with gcc 4.3/4.4 ?

[Comment 8 Mart Raudsepp 2009-09-28 14:01:23 UTC]

Packages in tree must not enable -Werror on their own. Robert, You should try to get rid of that, it can cause failures on innocent gcc warnings that aren't possible to remove completely, because different toolchain and compiler versions can have a different set of warning triggers, some of which could collide (one warns and if you fix it the other version warns, etc).
-Werror should be only an upstream tool that is enabled only in development builds or versions; then again, you ARE using a development snapshot version apparently, so upstream might be already disabling -Werror on proper releases (worth checking) but you need to patch it out for the snapshot in-tree

[Comment 9 Mart Raudsepp 2009-09-28 14:02:16 UTC]

Of course the warning that happens here can actually have very bad effects, worth following up the specific warning with upstream regardless of the -Werror issue

[Comment 10 Robert Piasek (RETIRED) 2009-09-28 14:35:20 UTC]

Mart,
Thanks for pointing that out. It's enabled by default in development code and controlled by configure switch. I've disabled it now.

Gene,
I've uploaded new snapshot of modemmananger - could you please try it, and let me know if you can reproduce this problem?

Thanks,
Rob

[Comment 11 Gene Imes 2009-10-08 22:50:57 UTC]

(In reply to comment #10)

> Gene,
> I've uploaded new snapshot of modemmananger - could you please try it, and let
> me know if you can reproduce this problem?
> 
> Thanks,
> Rob
> 

Thanks, Rob. Sorry for the delay.

modemmanager-0.2_p20090925 emerges fine.

I know this is not part of the bug but how do get modemmanager to work with Networkmanager?

Thanks again,

Gene

[Comment 12 Robert Piasek (RETIRED) 2009-10-09 10:07:03 UTC]

New version of NetworkManager (0.8) requires ModemManager to handle mobile phones/broadband connections. Currently there's a snapshot of NM 0.8 in portage tree - so just emerge it and you can test it.

There will be newer snapshots, as soon as policykit-0.9x gets back to portage tree (current snapshot of NM 0.8 depends on >=policykit-0.92).

Also newer version of connman will also make use of modemmanager (some code already landed there, but I don't think it usable yet).

R