[ros-bugs] [Bug 3031] Undefined symbolic constant in dc.c

ReactOS.Bugzilla at www.reactos.org ReactOS.Bugzilla at www.reactos.org
Sun Feb 3 19:03:16 CET 2008


http://www.reactos.org/bugzilla/show_bug.cgi?id=3031


Jeronimus Linuxius <jeronimus.linuxius at sapo.pt> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #4 from Jeronimus Linuxius <jeronimus.linuxius at sapo.pt>  2008-02-03 19:03:16 CET ---
(In reply to comment #2)
> If I recall correctly, we changed the path for such autogenerated files some
> time ago, so that the "bugcodes.h" file will now be generated in the
> "obj-i386" directory.

When I want to clean the source, I usually delete obj-i386/, outputi386/,
reactos/ and makefile.auto. I thought it was enough...

> Unfortunately, this means that there can still be an old version of
> this file, which is in another directory and not updated.

Thanks. I understand the idea. The static headers are still in include/, which
appears first in the include search path that is passed to the preprocessor.
So, cpp finds the old (autogenerated, cause if this file was static, svn up
would have removed it) bugcodes.h and includes it, and preprocesses the source
without even looking for the correct bugcodes.h (it must have been generated,
however, because of the make dependencies).

> Therefore I recommend you to get a new checkout of the ReactOS sources.
> When you do a clean build afterwards, the file should only be generated in one
> directory and your problem should be gone.

Thanks. I know what to do: delete includes/ and then do a svn up to restore the
static crowd...

In this case, the bug is invalid. Thank you once again...

JJ


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the Ros-bugs mailing list