50498 0 true 2009-08-04T23:43:29+02:00 65150 2009-08-07T00:00:00+02:00 47096 56 conflict-with-sysmacrosh-on-gentoo-linux 1 27230 resolved gentoo sysmacros.h 2009-08-08T19:17:03+02:00 50498 ayoy dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 0.8.3 under gentoo linux, the macros in /usr/include/sys/sysmacros.h rewrite the minor() and major() functions as gnu_dev_minor() and gnu_dev_major. easiest solution was to just change the naming of these function names to something else. under gentoo linux, the macros in /usr/include/sys/sysmacros.h rewrite the minor() and major() functions as gnu_dev_minor() and gnu_dev_major. easiest solution was to just change the naming of these function names to something else. <div><p>under gentoo linux, the macros in /usr/include/sys/sysmacros.h rewrite the minor() and major() functions as gnu_dev_minor() and gnu_dev_major. easiest solution was to just change the naming of these function names to something else.</p></div> 50498 0 under gentoo linux, the macros in /usr/include/sys/sysmacros.h rewrite the minor() and major() functions as gnu_dev_minor() and gnu_dev_major. easiest solution was to just change the naming of these function names to something else. <div><p>under gentoo linux, the macros in /usr/include/sys/sysmacros.h rewrite the minor() and major() functions as gnu_dev_minor() and gnu_dev_major.<br> easiest solution was to just change the naming of these function names to something else.</p></div> false 2009-08-04T23:43:29+02:00 65150 --- {} 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 new 2009-08-04T23:43:32+02:00 65150 dissolve dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 50498 0 Hi, thanks for reporting. Do you mean the `minor` and `major` fields of `AppVersion` struct? <div><p>Hi, thanks for reporting. Do you mean the <code>minor</code> and <code>major</code> fields of <code>AppVersion</code> struct?</p></div> false 2009-08-05T08:20:11+02:00 65150 --- {} 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 new 2009-08-05T08:20:14+02:00 50498 ayoy dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 50498 0 Sorry, yes. The problem is that the preprocessor doesn't seem to know the difference between a function call and the defaulted values on lines 30 and 31 of configfile.cpp Just moving those assignments inside the function fixes the problem too. Sorry, didn't look at it as closely before i just renamed the fields quickly, and I was lacking sleep. define commands from sysmacros.h /* Access the functions with their traditional names. */ # define major(dev) gnu_dev_major (dev) # define minor(dev) gnu_dev_minor (dev) I'm more curious why it really needs to pull in sysmacros.h at all. Seems silly that if anyone names a function minor or major they will get changed by it. <div><p>Sorry, yes. The problem is that the preprocessor doesn't seem to know the difference between a function call and the defaulted values on lines 30 and 31 of configfile.cpp<br> Just moving those assignments inside the function fixes the problem too.</p> <p>Sorry, didn't look at it as closely before i just renamed the fields quickly, and I was lacking sleep.</p> <p>define commands from sysmacros.h</p> <p>/ <em>Access the functions with their traditional names.</em> /</p> <h1>define major(dev) gnu_dev_major (dev)</h1> <h1>define minor(dev) gnu_dev_minor (dev)</h1> <p>I'm more curious why it really needs to pull in sysmacros.h at all. Seems silly that if anyone names a function minor or major they will get changed by it.</p></div> false 2009-08-07T06:42:43+02:00 65150 --- {} 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 new 2009-08-07T06:42:47+02:00 65150 dissolve dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 50498 0 Fixed that issue in git: commit 3d9ad4dc2b7459aee7ac1077943904b5b54bf00c Author: Dominik Kapusta <d@ayoy.net> Date: Fri Aug 7 17:57:01 2009 +0300 Changed AppVersion::m{aj,in}or to AppVersion::m{aj,in}orVer in order to avoid ambiguity when including sysmacros.h - some configurations apparently need to use it (?) I have to say that I find it really strange, since I'm using Gentoo Linux and maintaining qTwitter there, and I didn't experience this issue (and I have `sysmacros.h`, I guess every system has it ;) ). And I'm not including `sysmacros.h` anywhere, also by quick greping through the Qt source code I don't find anything suspicious. Do you use architecture other than x86/amd64? Anyway, I'm about to tag and release the new version with minor changes, mainly due to QOAuth library being mostly feature-complete - which required reorganizing its internals and API a bit ;) Expect qTwitter 0.8.3 within hours in qting-edge overlay and tomorrow in portage I guess :) <div><p>Fixed that issue in git:</p> <pre> <code>commit 3d9ad4dc2b7459aee7ac1077943904b5b54bf00c Author: Dominik Kapusta &lt;d@ayoy.net&gt; Date: Fri Aug 7 17:57:01 2009 +0300 Changed AppVersion::m{aj,in}or to AppVersion::m{aj,in}orVer in order to avoid ambiguity when including sysmacros.h - some configurations apparently need to use it (?)</code> </pre> <p>I have to say that I find it really strange, since I'm using Gentoo Linux and maintaining qTwitter there, and I didn't experience this issue (and I have <code>sysmacros.h</code>, I guess every system has it ;) ). And I'm not including <code>sysmacros.h</code> anywhere, also by quick greping through the Qt source code I don't find anything suspicious. Do you use architecture other than x86/amd64?</p> <p>Anyway, I'm about to tag and release the new version with minor changes, mainly due to QOAuth library being mostly feature-complete - which required reorganizing its internals and API a bit ;) Expect qTwitter 0.8.3 within hours in qting-edge overlay and tomorrow in portage I guess :)</p></div> true 2009-08-07T18:54:12+02:00 65150 --- :tag: :state: new :milestone: 47096 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 resolved gentoo sysmacros.h 2009-08-07T18:54:12+02:00 50498 ayoy dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 0.8.3 50498 0 Actually, I tried in on my home amd64 and an x86 running in my department, both had the same problem installing 0.8.2. It took a bit of searching but this looks like stdlib.h includes sys/types.h includes sys/sysmacros.h /usr/include/qt4/QtCore/qvector.h:#include <stdlib.h> /usr/include/qt4/Qt/qtestevent.h:#include <stdlib.h> /usr/include/qt4/Qt/qvector.h:#include <stdlib.h> /usr/include/qt4/QtTest/qtestevent.h:#include <stdlib.h> I tried tracing it through all of qt back up, but that got messy as hell. Curious though, why don't you get those inclusions. Different version of qt? <div><p>Actually, I tried in on my home amd64 and an x86 running in my department, both had the same problem installing 0.8.2.<br> It took a bit of searching but this looks like stdlib.h includes sys/types.h includes sys/sysmacros.h</p> <p>/usr/include/qt4/QtCore/qvector.h:#include &lt;stdlib.h&gt; /usr/include/qt4/Qt/qtestevent.h:#include &lt;stdlib.h&gt; /usr/include/qt4/Qt/qvector.h:#include &lt;stdlib.h&gt; /usr/include/qt4/QtTest/qtestevent.h:#include &lt;stdlib.h&gt;</p> <p>I tried tracing it through all of qt back up, but that got messy as hell.<br> Curious though, why don't you get those inclusions. Different version of qt?</p></div> true 2009-08-08T06:32:22+02:00 65150 --- {} 47096 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 resolved gentoo sysmacros.h 2009-08-08T06:32:26+02:00 65150 dissolve dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 0.8.3 50498 0 No idea, I've got Qt 4.5.2, the latest official. Anyway, qTwitter 0.8.3 with QOAuth 1.0 are in qting-edge now, and are joining Portage in a moment. Thanks for pointing out the issue! <div><p>No idea, I've got Qt 4.5.2, the latest official. Anyway, qTwitter 0.8.3 with QOAuth 1.0 are in qting-edge now, and are joining Portage in a moment. Thanks for pointing out the issue!</p></div> true 2009-08-08T19:17:00+02:00 65150 --- {} 47096 56 conflict-with-sysmacrosh-on-gentoo-linux 0 27230 resolved gentoo sysmacros.h 2009-08-08T19:17:03+02:00 50498 ayoy dissolve ayoy http://ayoy.lighthouseapp.com/projects/27230/tickets/56 0.8.3