[OpenAFS-win32-devel] afs_config manifest error while compliling openafs under visual studio 2008

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6CB7E1B5F105A794011012EC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have confirmed that both the openafs-stable-1_6_x and master branches
build for 64-bit and 32-bit with Visual Studio 2008 SP1 (15.00.30729.01)
and the Windows 6.1 SDK.

The below error is most likely caused by a tool chain misconfiguration.
 For example, compiling with the SDK compiler and linking with the
Visual Studio runtime libraries.

Jeffrey Altman

On 3/28/2011 2:56 AM, Gautam U Raut wrote:
> Hi All,
>=20
> While compiling openafs 1.5.78 under MS Visual studio 2008 for 64 bit,
> we get manifest error as =20
>=20
> C:\gautam\openafs-1.5.78\dest\amd64_w2k\free\root.client\usr\vice\etc\a=
fs_config.exe.manifest
> : manifest authoring error
> ttribute "level" not equal in different manifest snippets.
> NMAKE : fatal error U1077: 'if' : return code '0x1f'
>=20
> afs_config.exe.manifest has
>=20
> <?xml version=3D'1.0' encoding=3D'UTF-8' standalone=3D'yes'?>
> <assembly xmlns=3D'urn:schemas-microsoft-com:asm.v1' manifestVersion=3D=
'1.0'>
>   <trustInfo xmlns=3D"urn:schemas-microsoft-com:asm.v3">
>     <security>
>       <requestedPrivileges>
>         <requestedExecutionLevel level=3D'asInvoker' uiAccess=3D'false'=
 />
>       </requestedPrivileges>
>     </security>
>   </trustInfo>
>   <dependency>
>     <dependentAssembly>
>       <assemblyIdentity type=3D'win32' name=3D'Microsoft.VC90.CRT'
> version=3D'9.0.21022.8' processorArchitecture=3D'amd64'
> publicKeyToken=3D'1fc8b3b9a1e18e3b' />
>     </dependentAssembly>
>   </dependency>
> </assembly>
>=20
>=20
> If I change the level attribute to 'requireAdministrator', and then
> again fire "nmake /f NTMakefile install" command then build finishes
> successfully.
> But afs_config.exe fails to execute and shows errors such as MSVCR90.dl=
l
> is missing.
>=20
> Let me know possible solution.
>=20
> Regards,
> Gautam


--------------enig6CB7E1B5F105A794011012EC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJNw/vIAAoJENxm1CNJffh42isIAKSSV9eQMFSA5bMGDEe4ES5u
ptM/H5ZF8mzDSqLM8F4EtuxJPQC1GgEcSbhUI0OFgkc36wKOhlAx0wRrqjoCPU3J
y2wFTH4SeR4a6JstE8sQgJwd/JzoW381ld3/s8fBE9uuOLqDX4Bpc8WNbn0y0Cb3
EY/l64I12cZVtswbvcKdCwE6Cce4RrczWGKuOMXAxCyn+/GrLH0SmmKeSt2vQ2m2
rHcwhS2BP9cz65txEZoruefqBEsfCDPfQ7MlbTY4dEjMecWi95GH4pcQWH220y1q
WD6MnqfzE1NPuAdoMXndw3Pg62LLUrBfzmOKaNJeYv/Id+3sIGSNMNVC1KAvaFI=
=KcHZ
-----END PGP SIGNATURE-----

--------------enig6CB7E1B5F105A794011012EC--