tree d1bbba974539f91feb9dab6bb9852764d782184e
parent 62f3820b3197e9f4cef781411d7d2e2f8fc36f71
author Adriana Kobylak <anoo@us.ibm.com> 1606928895 -0600
committer Adriana Kobylak <anoo@us.ibm.com> 1606930170 -0600

obmc-flash-bmc: Specify full path for mktemp

Some eMMC systems report the following error when updating u-boot:

Dec 02 18:14:40 openbmc systemd[1]: Starting Write image 3ca0afa1 to BMC storage...
Dec 02 18:14:41 openbmc obmc-flash-bmc[507]: mktemp: (null): Read-only file system
Dec 02 18:14:41 openbmc obmc-flash-bmc[508]: dd: can't open '': No such file or directory
Dec 02 18:14:41 openbmc obmc-flash-bmc[510]: /usr/bin/obmc-flash-bmc: line 462: : No such file or directory

It appears that the TMPDIR variable is not set in that environment,
even though that a manual mktemp command works, so may be tied to
the script running in a bash shell.

In any case, specify the full path for the mktemp directory so that
it creates the file in /tmp/ and doesn't attempt to create it in
the running rootfs directory which is read-only.

Tested: Error was not seeing in the failing system and u-boot was updated.

Change-Id: I407a1e4f0d185d8fbb1e4f939bf8283246299a2d
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>