RTOS/TM4C129ENCPDT: build of wolfssl fails

Update:

After all of the above, I tried to repeat the build in the CCS 7 install (what I had started with) expecting to recover the error message that sent me down the path to switch from the 3.10 wolfssl to the 3.9.6 version.  However, now I only get the  Gmake: *** No rule to make target ‘uf’ stop  (BTW: I tried to insert a screen capture of the console but for some reason, the "Paste from Word" does not work in my environment).

I have searched several variations of this error but have not found any info on what might cause this. Maybe something in my environment (for CCS7) has changed since the build no longer begins?

Can you attach or copy-paste your products.mak file that you edited?

Also, it might help to see your wolfssl.mak file as well to make sure I see what you're actually using, please attach or cut-paste.

Regards,

- Rob

HI Rob,

I just attached (I think) the two file you requested - used the insert/attach media icon but that rejected when I tried to post. So I've copied the content from the two files:

#  ======== products.mak ========
#
#
# Read the processors.wiki.ti.com/.../Using_wolfSSL_with_TI-RTOS
# for instructions to download the software required.

#set XDCTOOLS_JAVA_HOME = C:/ti/ccsv6/eclipse/jre

# XDC_INSTALL_DIR is the path to XDCtools directory.
XDC_INSTALL_DIR        = C:/ti/tirex-content/xdctools_3_32_00_06_core

# BIOS_INSTALL_DIR is the path to TI-RTOS Kernel (SYS/BIOS) directory. If you
# have installed TI-RTOS, it is located in the products/bios_* path.
BIOS_INSTALL_DIR       = C:/ti/tirex-content/tirtos_tivac_2_16_00_08/products/bios_6_45_01_29

# NDK_INSTALL_DIR is the path to TI-RTOS NDK directory. If you have
# installed TI-RTOS, it is located in the products/ndk_* path.
NDK_INSTALL_DIR        = C:/ti/tirex-content/tirtos_tivac_2_16_00_08/products/ndk_2_25_00_09

# TIVAWARE_INSTALL_DIR is the path to Tivaware driverlib directory. If you have
# installed TI-RTOS, it is located in the products/TivaWare_* path.
TIVAWARE_INSTALL_DIR   = C:/ti/tirex-content/tirtos_tivac_2_16_00_08/products/TivaWare_C_Series-2.1.1.71b

# Define the code generation tools path for TI, IAR and GCC ARM compilers.
# If you have installed Code Composer Studio, the TI and GCC compiler are
# located in the ccsv*/tools/compiler/* path.
#
# Leave assignment empty to disable any toolchain.
ti.targets.arm.elf.M4F = C:/ti/CCS620/ccsv6/tools/compiler/arm_15.12.3.LTS
iar.targets.arm.M4F    =
gnu.targets.arm.M4F    =

-------------------------------------------------------------------------------------------------------------------------------------------------

#  ======== wolfssl.mak ========
#
include ./products.mak

# Enable older TI-RTOS 2.14-based variables
ifeq ($(BIOS_INSTALL_DIR),)
    BIOS_INSTALL_DIR=$(SYSBIOS_INSTALL_DIR)
endif
ifeq ($(TIVAWARE_INSTALL_DIR),)
    TIVAWARE_INSTALL_DIR=$(TIVAWARE)
endif

WOLFSSL_INSTALL_DIR=$(CURDIR)/../

#
# Set XDCARGS to some of the variables above.  XDCARGS are passed
# to the XDC build engine... which will load wolfssl.bld... which will
# extract these variables and use them to determine what to build and which
# toolchains to use.
#
# Note that not all of these variables need to be set to something valid.
# Unfortunately, since these vars are unconditionally assigned, your build line
# will be longer and more noisy than necessary.
#
# Some background is here:
#     rtsc.eclipse.org/.../Command_-_xdc
#
XDCARGS= \
    ti.targets.arm.elf.M4F=\"$(ti.targets.arm.elf.M4F)\" \
    gnu.targets.arm.M4F=\"$(gnu.targets.arm.M4F)\" \
    iar.targets.arm.M4F=\"$(iar.targets.arm.M4F)\" \
    NDK=\"$(NDK_INSTALL_DIR)\"

#
# Set XDCPATH to contain necessary repositories.
#
XDCPATH = $(BIOS_INSTALL_DIR)/packages;$(NDK_INSTALL_DIR)/packages;$(WOLFSSL_INSTALL_DIR);$(TIVAWARE_INSTALL_DIR)
export XDCPATH

#
# Set XDCOPTIONS.  Use -v for a verbose build.
#
#XDCOPTIONS=v
export XDCOPTIONS

#
# Set XDC executable command
# Note that XDCBUILDCFG points to the wolfssl.bld file which uses
# the arguments specified by XDCARGS
#
XDC = $(XDC_INSTALL_DIR)/xdc XDCARGS="$(XDCARGS)" XDCBUILDCFG=./wolfssl.bld

######################################################
## Shouldnt have to modify anything below this line ##
######################################################

all:
 @ echo building wolfssl packages ...
 @ $(XDC) -Pr ./packages

clean:
 @ echo cleaning wolfssl packages ...
 @ $(XDC) clean -Pr ./packages

-------------------------------------------------------------------------------------------------------------------------------------------------

I've checked and rechecked the paths in the products.mak and all appear to match installed locations.

Thank you for taking a look.

Update #2:

After poking around StackExchange, tried two things:

1) Change file/folder permissions to include modify/write for all users. No change, still get same error

2) Commented out the last two lines in the products.mak file (that had dangling '=') . No change, still get same error

Also, just to make sure no strange char got inserted into the products.mak file, ran 'type products.mak' in the Win Cmd window. Resulting output looks as expected.

So I'm still baffled. There has to be a clue in the fact that the first iteration of building wolfssl in the original wolfssl Ver 3.10 and CCS Ver 7 that I had downloaded, ran thru the build process for a fairly long time before stopping on some error with a missing file. Since then, I had switched over to an entirely new ti and wolfssl download/install folders, leaving the original untouched (FAIK), and now re-trying to run the same build in that Ver 7 fails in the same manner as I've consistently got with the second iteration. BTW: running with the CLEAN option (in place of ALL) causes the same error.