Specifying which machine we're building for memd changes

Due to the manner in which fspCI compiles, we were having
an issue where a placeholder file was being overwritten
by its counterpart for another machine.  This commit moves
the placeholder file from the common directory to the
specific machine directory.

Change-Id: I4ba995f71b41848510e165cb64a802d8041c080d
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/48141
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Reviewed-by: Martin Gloff <mgloff@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

src/build/buildpnor/memd_creation.pl

@@ -115,7 +115,7 @@
     }
 
     # Removing the first byte of the MEMD binary
-    my $new_file = "edited_memd.dat";
+    my $new_file = "$memd_dir/edited_memd.dat";
     run_command("tail -c +2 $file > $new_file");
     run_command("mv $new_file $file");