Re: [PATCH] portable use of mktemp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 15, 2018 at 04:55:16PM +0100, Ramsay Jones wrote:
> 
> 
> On 15/06/18 05:37, Luc Van Oostenryck wrote:
> > Most manpages for mktemp(1) specify that the 'XXXXXX' part of the
> > template must be at the end (of course, the GNU's version accept
> > it anywhere). At least the busybox's version used by Alpine Linux
> > tries to enforce that and fails in sparse current use of it:
> > 	tmp.XXXXXX.{llvm,o}
> > 
> > Fix that by moving the XXXXXX at the end like:
> > 	tmp.{l,o}.XXXXXX
> > 
> > Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
> 
> I recently noticed that I have duplicated your earlier commit
> a410611d7a ("llvm: fix creation of sparsec's tmp files", 2017-03-27),

Mmmm. I had forgot I had made this patch.
It's kinda interesting because the current problem was not present
back then.

> while doing a test merge with the master branch of your 'sparse.git'
> repo (ie _not_ your sparse-dev.git repo).

For info, the master branch is always the same in both repos.
 
> [I'm developing on top of v0.5.2 - a410611d7a was in a side branch
> and not in the v0.5.2 release.]

I understand that people prefer to develop on top of the official
tree but my tree have dozens and dozens of bugfixes that are not
yet present in the official one.

> FWIW, I think I prefer to tmp-directory idea in a later email.

OK, I take note and I'll wait a bit for Josh's opinion.
 
Best regards,
-- Luc
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux