On Sun, March 30, 2008 11:41 pm, Phil Dibowitz wrote:
> And again, you missed what I said about declarations not at the top. This
> is why we use -ansi -pedantic-errors:
>
> [EMAIL PROTECTED] tmp]$ gcc -std=c99 foo.c
> [EMAIL PROTECTED] tmp]$ gcc -std=c99 -pedantic-errors foo.c
> [EMAIL PROTECTED]
Stephen Warren wrote:
> On Sun, March 30, 2008 11:41 pm, Phil Dibowitz wrote:
>> And again, you missed what I said about declarations not at the top. This
>> is why we use -ansi -pedantic-errors:
>>
>> [EMAIL PROTECTED] tmp]$ gcc -std=c99 foo.c
>> [EMAIL PROTECTED] tmp]$ gcc -std=c99 -pedantic-erro
On Mon, March 31, 2008 11:38 am, Phil Dibowitz wrote:
> Stephen Warren wrote:
>> On Sun, March 30, 2008 11:41 pm, Phil Dibowitz wrote:
>>> And again, you missed what I said about declarations not at the top.
>>> This
>>> is why we use -ansi -pedantic-errors:
>>>
>>> [EMAIL PROTECTED] tmp]$ gcc -std
Well, thanks for your precious time...
Seems like all this 'Harmony vs. Concordance', 'LINUX vs. Windows'
and 'ANSI vs. C99' stuff has settled enough to try and merge my
other two patches, so here just a few short notes to your comments:
On Monday 31 March 2008, Phil Dibowitz wrote:
> OK, I spen
Stephen Warren wrote:
> * It certainly won't remove the warning about strdup not being prototyped
> (that's due to -ansi), which is a warning for me, but I believe an error
> on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
> of headers to help packaging libconcord on Fedo
Stephen Warren wrote:
> * It certainly won't remove the warning about strdup not being prototyped
> (that's due to -ansi), which is a warning for me, but I believe an error
> on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
> of headers to help packaging libconcord on Fedor
Stefan Arndt wrote:
> Hello,
>
> I reversed the former patch and patched with the new one.
OK, I see the problem (or at least *a* problem). Looking back at the USB
logs, we need to write a 0, not a 1 to address 20. I've committed a fix
to CVS, reverse the patch, cvs update, and try again.
--
Hello,
got the files all new from cvs.
Furthermore only 2 of my three usb ports on my
laptop work. If the remote is attached to one of them, concordance
did not find the remote.
localhost:/home/arndt/Documents/concordance # concordance -F firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin T
Stefan Arndt wrote:
> Hello,
>
> got the files all new from cvs.
>
> Furthermore only 2 of my three usb ports on my
> laptop work. If the remote is attached to one of them, concordance
> did not find the remote.
Well, then make sure you're always using a good one!
> DEBUG (HID_ReadReport): Fail
Yes, switching from -pedantic-errors to -pedantic switches the varargs
error to a warning.
Note that the error/warning is pretty clear; varargs macros only exist
in C99 plus, so if we're claiming to have C89 source via -ansi, we can't
use them.
Build logs:
# Fedora 8, gcc 4.1.2:
gcc (GCC) 4.1.2
Hello,
well, it is getting better.
But only sort of...
It looks like it does not really writes the firmware.
It is still 2.1
localhost:/home/arndt/Documents # concordance -F LatestFirmware\(3\).EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distribu
Phil Dibowitz wrote:
> Stephen Warren wrote:
>> * It certainly won't remove the warning about strdup not being prototyped
>> (that's due to -ansi), which is a warning for me, but I believe an error
>> on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
>> of headers to help pa
Phil Dibowitz wrote:
> Update of /cvsroot/concordance/concordance/concordance
> In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv28807
>
> Modified Files:
> concordance.c
> Log Message:
> Get rid of that silly strdup() warning.
Just FYI, it looks like, on Linux at least, if you define
Stephen Warren wrote:
> Phil Dibowitz wrote:
>> Stephen Warren wrote:
>>> * It certainly won't remove the warning about strdup not being prototyped
>>> (that's due to -ansi), which is a warning for me, but I believe an error
>>> on gcc-4.3 (hence why I submitted the patch for libconcord to add a bu
Phil Dibowitz wrote:
> Stephen Warren wrote:
>> It appears there is a gcc option -Wno-variadic-macros.
>
> I'm cool with that - though I would like to confirm the current source does
> in fact build in windows before I nuke the warning
Hmm. MSDN says Visual C++ 2005 does, but that means Visua
Stephen Warren wrote:
> Phil Dibowitz wrote:
>> Update of /cvsroot/concordance/concordance/concordance
>> In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv28807
>>
>> Modified Files:
>> concordance.c
>> Log Message:
>> Get rid of that silly strdup() warning.
>
> Just FYI, it looks like,
Stephen Warren wrote:
> Phil Dibowitz wrote:
>> Stephen Warren wrote:
>>> * It certainly won't remove the warning about strdup not being prototyped
>>> (that's due to -ansi), which is a warning for me, but I believe an error
>>> on gcc-4.3 (hence why I submitted the patch for libconcord to add a bu
Stefan Arndt wrote:
> Hello,
>
> well, it is getting better.
>
> But only sort of...
Yeah, I didn't expect that'd lead to much good.
Can you send me the firmware file you're using? I'm at a bit of a loss at
this point...
--
Phil Dibowitz [EMAIL PROTECTED]
Open Sour
Phil Dibowitz wrote:
> It's so weird I don't get the same behavior...
> [variadic macros error from gcc]
Yes indeed.
I installed a Debian sid chroot on my Fedora 8 system using the
debootstrap utility, and installed the gcc-4.3 and g++-4.3 packages
using aptitude (Debian seems crazy fast download
19 matches
Mail list logo
