I am getting duplicate reference definition warning while building jupyter-book, also I could not find which reference definition is duplicated. How can I avoid from this warning or how can I suppress this warning in config.yml file?
WARNING: Duplicate reference definition: // [myst.ref]
I try to add suppress warnings for duplicated bibtex references but I could not handle it.
Related
I have the problem with compilation. After adding function call
otThreadGetMaxAllowedChildren() in the openthread/examples/apps/cli/main.c I got an error:
openthread/examples/apps/cli/main.c:228: undefined reference to `otThreadGetMaxAllowedChildren'
Similary, the same issue with otThreadGetChildInfoByIndex():
openthread/examples/apps/cli/main.c:204: undefined reference to `otThreadGetChildInfoByIndex'
I have added -DOPENTHREAD_FTD=1 flag, but error still occurs.
Any idea what should I do to make compilation successful?
The otThreadGetChildInfoByIndex() is only available for FTD builds.
You should either:
Disable MTD and RCP in your build options, or
Wrap your child table code with #if OPENTHREAD_FTD.
You can refer to the CLI code for example usage.
I'm using STM32Cube to generate an IAR EW 8.2 project with FreeRTOS 10.0.1 and CMSISv2 API's. When I clean up the project and build again, I get the following warnings
Warning[Pe177]: variable "hTask" was declared but never referenced
Warning[Pe177]: variable "hTimer" was declared but never referenced
Warning[Pe177]: variable "hEventGroup" was declared but never referenced
Warning[Pe177]: variable "hSemaphore" was declared but never referenced
Warning[Pe177]: variable "hQueue" was declared but never referenced
I know that these warnings should not affect my code but I would be interested if this warnings are always there or if they depend on my settings.
These are warnings being generated by IAR's compiler. They'll go away after those variables are used. If they aren't used. . . get rid of them and the warnings will also go away ;-) Dead code is never a good thing to keep around! Specifically, you should really consider treating warnings more like errors, since it will force a cleaner code base.
If you really want to supress warnings, you can mask individual warnings in IAR:
1. Select Project-->Options-->Compiler tab
2. Select Suppress these diagnostics and specify your desired warning
3. Click OK.
I have a workflow containing 3 activities. The external variable that is used throughout the workflow is of type Dictionary which contains only two fields: EmailAddress and PhoneNumber(all strings). This is the screenshot of the workflow
So the scenario is that the activity GetParticipant has an outargument of type Dictionary which I am assigning to an external variable called pax. Using the if condition I am checking if the EmailAddress is provided or not.
My problem is that I am getting an error at the if condition:
Reference required to assembly 'Microsoft.WindowsAzure.Storage, Version=4.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' containing the base class 'Microsoft.WindowsAzure.Storage.Table.TableEntity'. Add one to your project.
The mentioned reference is already added to the project and the workflow also imports it. But the error remains. However giving only True as the condition works. What am I doing wrong?
Its seems some reference issue as i can see one bubble near if condition.
Check for dependency of mentioned Dll, can use nugget manager.
You can do below steps.
Delete reference of dll and import.
Clean solution and add reference and set property copy local true and import the namespace in workflow.
Rebuild the solution.
When running doxygen over one particular pretty large C-language project consisting many files (all completely documented, I think), then I always find this warning at the bottom of the output:
<#1>:1: warning: parameters of member #1 are not (all) documented
How can I find and remove the trigger of this warning?
Note that the project in question is too large (and the issue not important enough) for bisection or other trial and error based search methods.
Realize this is an old question but just ran into this behaviour myself and didn't find a solution online.
Found the offending file by running Doxygen and looking at where the error message appears in the output (make sure you're not suppressing stdout or you'll just get the error with no context).
In my case the error appeared after the line "Generating dependency graph for group [name]". By looking at the relevant file I found an undocumented, unnamed enum. The members of the enum were still documented. e.g.
enum
{
X = 1, /**< Documented. */
...
}
I'm guessing it's the lack of name on the enum that was throwing Doxygen and causing the unhelpful message. Adding a name causes more helpful error messages to be generated. Documenting the enum (with or without a name) removes the error.
From the error I am getting:
ld: duplicate symbol _main in /Users/wostler/Library/Developer/Xcode/DerivedData/UIPageViewControllerDemo-hjsgatcuhsxeokdnubifybpivzum/Build/Intermediates/UIPageViewControllerDemo.build/Debug-iphonesimulator/UIPageViewControllerDemo.build/Objects-normal/i386/fmdb.o and /Users/wostler/Library/Developer/Xcode/DerivedData/UIPageViewControllerDemo-hjsgatcuhsxeokdnubifybpivzum/Build/Intermediates/UIPageViewControllerDemo.build/Debug-iphonesimulator/UIPageViewControllerDemo.build/Objects-normal/i386/main.o for architecture i386
I can't figure out why this error is occurring. I simply changed some framework files in my project and now this error won't go away! It obviously says _main is being duplicated, but I dont know where, or why?
What is causing this?
You need to look at the main.m/.h and fmdb.m/.h files. What is most likely is that they are both importing something that defines _main, perhaps at a global level. Usually thats the sort of thing that generates this error for me.
You have two main function in your code. Do a global search for main and remove the one you don't want.
It happens when you add some other project's files to your project without remove the main function.
Sounds like you have multiple entries under Targets/Compiled Sources. Check and remove them.