topic general error c1010070: Failed to load and parse the manifest in Intel® Fortran Compiler

general error c1010070: Failed to load and parse the manifest

Mike896 — Thu, 02 Oct 2008 08:30:32 GMT

Hi
  As I Build Solution, it appears:
Output Window 
Embedding manifest...
.\Debug\sdue2ae.exe.intermediate.manifest : general error c1010070: Failed to load and parse the manifest. {q~0H

I used to have problems of IMSL, but I have checked it and it seems ok.

I'd like to ask what the problem is.

Thanks a million.

Mike

Re: general error c1010070: Failed to load and parse the manife

Steven_L_Intel1 — Thu, 02 Oct 2008 12:41:36 GMT

I never saw that one before, but a Google search suggests that one possibility is too long a path for the manifest file. That does not seem to be your problem.

I suppose a simple solution is to disable generation of manifests. In the project properties, select Linker > Manifest File and change "Generate Manifest" to no. I doubt you will miss it.

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Fri, 03 Oct 2008 00:11:50 GMT

Quoting - Steve Lionel (Intel)

I never saw that one before, but a Google search suggests that one possibility is too long a path for the manifest file. That does not seem to be your problem.

I suppose a simple solution is to disable generation of manifests. In the project properties, select Linker > Manifest File and change "Generate Manifest" to no. I doubt you will miss it.

I''ve done it. But now it shows:

Embedding manifest...
mt.exe : general error c10100b1: Failed to load file ".Debugsdue2AE.exe". {q~0H

I've ReBuild or Clean the solution, it doesn't work either.

I've checked the *.obj files. They are not rebuilt at all. :(

Thank you for your help.

Mike

Re: general error c1010070: Failed to load and parse the manife

Steven_L_Intel1 — Fri, 03 Oct 2008 00:46:23 GMT

Are those strange characters which show in the post actually in the filename?

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Fri, 03 Oct 2008 01:02:26 GMT

Quoting - Steve Lionel (Intel)

Are those strange characters which show in the post actually in the filename?

No. The strange characters are outside the filename. The filename is correct.

Now, it shows:

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

There is no Buildlog in ./Debug/, no ***.obj. Silent. :(

Thanks for keeping help me.

Mike

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Fri, 03 Oct 2008 01:13:14 GMT

Quoting - Steve Lionel (Intel)

Are those strange characters which show in the post actually in the filename?

I started a new and very simple project now.

program main
print *,'sss'
end program main

After Build Solution, it shows:

1>------ Build started: Project: Console2, Configuration: Debug Win32 ------
1>
1>Build log written to "file://D:tempConsole2Console2DebugBuildLog.htm"
1>Console2 - 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

But I don't find the *.obj in ./Debug at all.

and Build Solution again,
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
Still no *.obj.

Then I Run it, it shows:

Visual Studio cannot debug because the debug target 'D:tempConsole2Console2debugconsole2.exe' is missing.

Mike

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Fri, 03 Oct 2008 02:14:27 GMT

Quoting - Mike896

I started a new and very simple project now.

program main
print *,'sss'
end program main

After Build Solution, it shows:

1>------ Build started: Project: Console2, Configuration: Debug Win32 ------
1>
1>Build log written to "file://D:tempConsole2Console2DebugBuildLog.htm"
1>Console2 - 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

But I don't find the *.obj in ./Debug at all.

and Build Solution again,
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
Still no *.obj.

Then I Run it, it shows:

Visual Studio cannot debug because the debug target 'D:tempConsole2Console2debugconsole2.exe' is missing.

:(

Mike

Oh, I find out that IVF will not automatically remind user to save the newly edited file and add to the project.

I remember CVF will do it.

After I save and add it to project, it works now.

But back to my previous post, it still shows

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

There is no new Buildlog in ./Debug/, no updated ***.obj. Silent. :(

Thanks for keeping help me.

Mike

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Fri, 03 Oct 2008 07:31:05 GMT

Quoting - Mike896

Oh, I find out that IVF will not automatically remind user to save the newly edited file and add to the project.

I remember CVF will do it.

After I save and add it to project, it works now.

But back to my previous post, it still shows

========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========

There is no new Buildlog in ./Debug/, no updated ***.obj. Silent. :(

Thanks for keeping help me.

Mike

I've redone one static-library project by collecting all the files(modules and external files) except main file.

This is done successfully.

I create a main project to add the main file and also linking thestatic library.

I compare the settings in Project->properties and find Fortran is missing in Configuration Properties for the old project.

Also there is also another Common Properties added.

Mike

Re: general error c1010070: Failed to load and parse the manife

Steven_L_Intel1 — Fri, 03 Oct 2008 13:19:52 GMT

Mike,

You will not see Fortran in the Configuration Properties. It will be in the Project Properties.

At this point I suggest that you enter an issue at Intel Premier Support and attach a ZIP of your solution folder. There's not enough information here so far to understand the problem.

Re: general error c1010070: Failed to load and parse the manife

Mike896 — Sat, 04 Oct 2008 00:19:52 GMT

Quoting - Steve Lionel (Intel)

Mike,

You will not see Fortran in the Configuration Properties. It will be in the Project Properties.

At this point I suggest that you enter an issue at Intel Premier Support and attach a ZIP of your solution folder. There's not enough information here so far to understand the problem.

Thank you for your information.

I find out I forgot to include *.mod. There are so many settings to be remebered and they appear in many places.

Mike