Chromium build fails after a while on Ubuntu - google-chrome

I am getting a build error after a while, and I am unsure as to why.
Any ideas or hints?

I was missing the
libc6:i386
package, which contains
/lib/ld-linux.so.2
needed to load shared libraries.
Without this, it prevented me from running various shared libraries, and merely said "no such file or directory" which is a crap error message imho since the file is clearly there, just not executable.

Related

Not able to deploy the Web App: "library with identifier is missing" error

I have deleted some older versions under file -> manage versions, keeping only the latest version.
After that, it is not loading the project properties and also not able to deploy the webapp.
When i tried to deploy the webapp, it is giving following error.
Library with identifier {project_name} is missing (perhaps it was deleted, or you don't have read access?)
Can anyone help, where it went wrong.

Integration of Yet Another Forum with the existing and running blog engine

i installed yet another forum code successfully.But when i tried to integrate it with blog engine 2.0 it is giving me error as follows:- Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.Can anyone suggest me the solution?
I think that you have choose Clean then you Rebuild your solution's cause Autofac dll sometime Don't get generated. To solve your problem either copy the Autfac.dll from your downloaded files and put them in the bin folder again. I have experienced this problem several times and this solved it.

Can't get Lazarus to do.....anything?

So I thought I would install Lazarus/Free pascal -latest version from the sourceforge website.
Downloaded the win32 version and install on my XP machine couple of nights ago.
Problem is, it can't seem to find any of its own files.
From the first and every subsequent run it comes up with an error which says it can't find its system.ppu file relating to win32.
I just ignore that error and it seems to still run.
I tried to make a simple calculator application and it couldn't even seem to find the system files or files in the project directory. After battling these problems and setting every single path I could find in all the setups to every directory I could find it eventually compiled and run the program - once, not been able to make it do it again.
I also tried to make a user component library following the instructions on the web and that won't work either because, you guessed it, it can't the files. This time it gives an error saying it can't find a Ttreeview component, despite not even using that component in the library.
Being able to follow search paths is pretty fundamental stuff that they don't seem to have mastered.
Anybody managed to get a working system going, or any tips to sort these problems out?
Did you install in the default directory c:\lazarus? I thought there was an issue with installing to another directory, especially if the path contains spaces.
Nine times out of ten, its the old config of an earlier Lazarus attempt, that still lingers somewhere in the "local app" part of the profile.
If nothing else helps uninstall Lazarus, download Lazarus CodeTyphon edition, and run install as admin.

Hudson: Error after creating doxygen files; downgrade not working either

I'm having the following problem with Hudson after upgrading to 2.1.0:
After successfully creating the doxygen output, the following exception occurs:
Publishing Doxygen HTML results.
The determined Doxygen directory is 'C:/doxy/myDir'.
FATAL: error
hudson.util.IOException2: java.io.IOException: Unconnected pipe
The error did not occur with 2.0.1, unfortunately, downgrading does not work - Hudson tells me, that it can't read the job files anymore.
Does anyone know the best way to deal with this? Is there a simple solution to either make the doxygen plugin work in 2.1.0 or to successfully downgrade to 2.0.1?
Not sure what exactly the problem was, but migrating to the newest Jenkins release and using the HTML report publisher plugin instead of the Doxygen plugin is at least a work

SSIS script task pre-compile script into binary code set to false

If I set pre-compile script into binary code to true I get error saying "The task is configured to pre-compile the script, but binary code is not found."
If I set this property to False then it works. Will it be a problem after I deploy package on production server?
Please advice.
The binary code would need to be pre-compiled if you are running production in 64-bit, is this the case? Sounds like there is a syntax error in your script code though, can you post it here so we can see what the problem might be?
You shouldn't have any problem if you don't have to deploy to a 64-bit machine. From MSDN:
If the script is precompiled it will
start more quickly and the script can
run in a 64-bit environment. However,
the package size is larger when it
contains precompiled scripts.
Moreover, compiled script cannot be
debugged
This a problem acknowledged by Microsoft (in Sql Server 2005), and you can find a fix here
Just to inform that I tried this update in my SQL Server and it never worked. I had to set precompile in the script task properties to off
In my simple C# script task, I was getting the error -
Package Validation Error
Error at Send Mail: The binary code for the script is not found. Please
open the script in the designer by clicking Edit Script button and
make sure it builds successfully. Error at Send Mail: There were
errors during task validation.
(Microsoft.DataTransformationServices.VsIntegration)
In my case I was just using a simple try catch block to catch Exception in simple code. I added a using System.Exception; I got the error after that. I just realized that this import is not needed and is the cause of the error. I don't know why it causes an error in SSIS.
In my case I had forgotten to add the reference to Microsoft.Exchange.WebServices.dll.
I was able to solve it by reading the official Microsoft documentation, which describes how to reference it.