public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tomas Pilar (tpilar)" <Tomas.Pilar@arm.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"df7729@gmail.com" <df7729@gmail.com>
Cc: nd <nd@arm.com>
Subject: Re: [edk2-devel] Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items?
Date: Tue, 26 May 2020 10:20:25 +0000	[thread overview]
Message-ID: <AM5PR0801MB1844BA043102340F458C4ED4E7B00@AM5PR0801MB1844.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <7AV9.1590393358635470204.j9Pi@groups.io>

[-- Attachment #1: Type: text/plain, Size: 10453 bytes --]

Based on the output, am I correct in assuming that the generated ABCPPSupportLib makefile does not have a rule for making ABCPPSupportLib.obj?

Tom

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of David F. via groups.io
Sent: 25 May 2020 08:56
To: devel@edk2.groups.io
Subject: [edk2-devel] Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items?

Hi,

I haven't updated the edk2 in quite a while, I went ahead and did it tonight, stdlib was removed so I had to move stuff around.  Where I used to have C:\EDK2, I now have C:\EDK\EDK2 and C:\EDK\EDK2-CLIB.   My private directory is still under C:\EDK\EDK2\Acme.   After figuring out how to get stdlib on its own repository by using the new directory, I then had to setup a batch file to do my edksetup in a different way.  Now has:
set WORKSPACE=%CD%
set PACKAGES_PATH=%WORKSPACE%\edk2-libc;%WORKSPACE%\edk2
set EDK_TOOLS_PATH=%WORKSPACE%\edk2\BaseTools
cd %WORKSPACE%\edk2
edksetup.bat

It's all looking pretty good.  I am using VS2008 for my EDK builds, I decided to stay with my old build_rule.txt, target.txt and tools_def.txt which has some older stuff in it that doesn't apply (I looked at the new stuff, but I have some custom switches and it wasn't much different).   So I run my build switch to build my UEFI application and it starts and builds some items, but then dies with the NMAKE failure and I have no clue why.   Here are some of the details after deleting c:\edk\build which is where it wants to go.
Build environment: Windows-10-10.0.18362
Build start time: 00:33:37, May.25 2020
WORKSPACE        = c:\edk
PACKAGES_PATH    = c:\edk\edk2-libc;c:\edk\edk2
EDK_TOOLS_PATH   = c:\edk\edk2\basetools
EDK_TOOLS_BIN    = c:\edk\edk2\basetools\bin\win32
CONF_PATH        = c:\edk\edk2\conf
PYTHON_COMMAND   = C:\python27-x64\python.exe
Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = VS2008x86
Active Platform          = c:\edk\edk2\Acme\Acme.dsc
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: c:\edk\edk2-libc\stdlib\libc\gdtoa\gdtoaimp.h not found in c:\edk\edk2-libc\StdLib\LibC\gdtoa\gdtoa.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: c:\edk\edk2-libc\stdlib\libc\gdtoa\gdtoa.h not found in c:\edk\edk2-libc\StdLib\LibC\gdtoa\gdtoa.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: c:\edk\edk2-libc\stdlib\libc\time\tzfile.h not found in c:\edk\edk2-libc\StdLib\LibC\Time\Time.inf
build: : warning: Module MetaFile [Sources] is missing local header!
  .... Several more like this from stdlib ....
Building ... c:\edk\edk2\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib.inf [X64]
Building ... c:\edk\edk2\Acme\Library\ABMemDumpLib\ABMemDumpLib.inf [X64]
Building ... c:\edk\edk2\Acme\Library\ABVSSupportLib\ABVSSupportLib.inf [X64]
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABLegacySpeakerLib  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64  /Ic:\edk\edk2\Acme  /Ic:\edk\edk2\Acme\Include  /Ic:\edk\edk2\Acme\Include\AB\UEFI  /Ic:\edk\edk2\Acme\Include\AB\fastgui  /Ic:\edk\edk2\Acme\Include\AB  /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib.c
Building ... c:\edk\edk2\Acme\Library\ABMountedCPPEntryLib\ABMountedCPPEntryLib.inf [X64]
Building ... c:\edk\edk2\Acme\Library\ABSafeOpenProtocolLib\ABSafeOpenProtocolLib.inf [X64]
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABMemDumpLib  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64  /Ic:\edk\edk2\Acme  /Ic:\edk\edk2\Acme\Include  /Ic:\edk\edk2\Acme\Include\AB\UEFI  /Ic:\edk\edk2\Acme\Include\AB\fastgui  /Ic:\edk\edk2\Acme\Include\AB  /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABMemDumpLib\ABMemDumpLib.c
Building ... c:\edk\edk2\MdePkg\Library\UefiApplicationEntryPoint\UefiApplicationEntryPoint.inf [X64]
ABLegacySpeakerLib.c
Building ... c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\BaseIoLibIntrinsic.inf [X64]
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABVSSupportLib\ABVSSupportLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABVSSupportLib  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABVSSupportLib\ABVSSupportLib\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64  /Ic:\edk\edk2\Acme  /Ic:\edk\edk2\Acme\Include  /Ic:\edk\edk2\Acme\Include\AB\UEFI  /Ic:\edk\edk2\Acme\Include\AB\fastgui  /Ic:\edk\edk2\Acme\Include\AB  /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABVSSupportLib\ABVSSupportLib.c
Building ... c:\edk\edk2\Acme\Library\ABCPPSupportLib\ABCPPSupportLib.inf [X64]
ABMemDumpLib.c
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\lib.exe" /NOLOGO /LTCG /OUT:c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\OUTPUT\ABLegacySpeakerLib.lib @c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABLegacySpeakerLib\ABLegacySpeakerLib\OUTPUT\object_files.lst
NMAKE : fatal error U1073: don't know how to make 'c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMountedCPPEntryLib\ABMountedCPPEntryLib\OUTPUT\ABMountedCPPEntryLib.obj'
Stop.
ABVSSupportLib.c
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABSafeOpenProtocolLib\ABSafeOpenProtocolLib\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\Acme\Library\ABSafeOpenProtocolLib  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABSafeOpenProtocolLib\ABSafeOpenProtocolLib\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64  /Ic:\edk\edk2\Acme  /Ic:\edk\edk2\Acme\Include  /Ic:\edk\edk2\Acme\Include\AB\UEFI  /Ic:\edk\edk2\Acme\Include\AB\fastgui  /Ic:\edk\edk2\Acme\Include\AB  /Ic:\edk\edk2\Acme\Include\IPP c:\edk\edk2\Acme\Library\ABSafeOpenProtocolLib\ABSafeOpenProtocolLib.c
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\lib.exe" /NOLOGO /LTCG /OUT:c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\OUTPUT\ABMemDumpLib.lib @c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMemDumpLib\ABMemDumpLib\OUTPUT\object_files.lst
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\MdePkg\Library\UefiApplicationEntryPoint\UefiApplicationEntryPoint\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\MdePkg\Library\UefiApplicationEntryPoint  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\MdePkg\Library\UefiApplicationEntryPoint\UefiApplicationEntryPoint\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64 c:\edk\edk2\MdePkg\Library\UefiApplicationEntryPoint\ApplicationEntryPoint.c
NMAKE : fatal error U1073: don't know how to make 'c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABCPPSupportLib\ABCPPSupportLib\OUTPUT\ABCPPSupportLib.obj'
Stop.
    "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\x86_amd64\cl.exe" /Foc:\edk\Build\Acme\RELEASE_VS2008x86\X64\MdePkg\Library\BaseIoLibIntrinsic\BaseIoLibIntrinsic\OUTPUT\.\ /nologo /c /WX /GS- /X /W4 /Gs32768 /O1ib2s /GL- /Gy /FIAutoGen.h /EHs-c- /GR- /GF /X /Zc:wchar_t- /D UEFI_C_SOURCE /D MDEPKG_NDEBUG /D NDEBUG /Ic:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\X64  /Ic:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic  /Ic:\edk\Build\Acme\RELEASE_VS2008x86\X64\MdePkg\Library\BaseIoLibIntrinsic\BaseIoLibIntrinsic\DEBUG  /Ic:\edk\edk2\MdePkg  /Ic:\edk\edk2\MdePkg\Include  /Ic:\edk\edk2\MdePkg\Include\X64 c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\IoLibMmioBuffer.c c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\IoHighLevel.c c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\IoLibMsc.c c:\edk\edk2\MdePkg\Library\BaseIoLibIntrinsic\IoLib.c
ABSafeOpenProtocolLib.c
build.py...
 : error 7000: Failed to execute command
    C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\nmake.exe /nologo tbuild [c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABCPPSupportLib\ABCPPSupportLib]
build.py...
 : error 7000: Failed to execute command
    C:\Program Files (x86)\Microsoft Visual Studio 9.0\Vc\bin\nmake.exe /nologo tbuild [c:\edk\Build\Acme\RELEASE_VS2008x86\X64\Acme\Library\ABMountedCPPEntryLib\ABMountedCPPEntryLib]
build.py...
 : error F002: Failed to build module
    c:\edk\edk2\Acme\Library\ABCPPSupportLib\ABCPPSupportLib.inf [X64, VS2008x86, RELEASE]
- Failed -
Build end time: 00:33:41, May.25 2020
Build total time: 00:00:04

Both of those that failed have:
[Packages]
 StdLib/StdLib.dec.
I'm not sure if that has something to do with it but the others built fine.   I looked for any differences in the .inf or .dec and .dsc but all looks fine.

There used to be a build-tools mailing list but it doesn't exist and could only find these new group/mailing lists.  Can someone help?   Is there a way to get more details on what it doesn't like?  Do I have to do something different now that the LIBC stuff is split up to their own folder?

TIA!!


[-- Attachment #2: Type: text/html, Size: 20432 bytes --]

      parent reply	other threads:[~2020-05-26 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  7:55 Updating to latest EDK2 and now get NMAKE: fatal error U1073: Don't know how to make.. on some items? df7729
2020-05-25 20:51 ` [edk2-devel] " Michael D Kinney
2020-05-25 23:21   ` Andrew Fish
2020-05-26  0:21     ` Guomin Jiang
2020-05-26  7:18       ` David F.
2020-05-27  0:06         ` Guomin Jiang
2020-05-26 10:20 ` Tomas Pilar (tpilar) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM5PR0801MB1844BA043102340F458C4ED4E7B00@AM5PR0801MB1844.eurprd08.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox