Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12241] Permission denied while running "make"
Date: Fri, 20 Sep 2019 06:58:06 +0000	[thread overview]
Message-ID: <bug-12241-163-eDx6bGsXG7@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12241-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12241

Cerem Cem ASLAN <ceremcem@ceremcem.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #4 from Cerem Cem ASLAN <ceremcem@ceremcem.net> ---
Exactly: 

ceremcem at cca-erik:~$  mount | grep -F /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,size=524288k)


I remounted with "exec": 

sudo mount -o remount,exec /tmp

Then compilation continued. Would you consider adding that checking into
makefile? (I may provide a patch for that)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-09-20  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 18:19 [Buildroot] [Bug 12241] New: Permission denied while running "make" bugzilla at busybox.net
2019-09-19 18:19 ` [Buildroot] [Bug 12241] " bugzilla at busybox.net
2019-09-19 19:42 ` bugzilla at busybox.net
2019-09-20  0:06 ` bugzilla at busybox.net
2019-09-20  0:29 ` bugzilla at busybox.net
2019-09-20  6:58 ` bugzilla at busybox.net [this message]
2019-09-20 11:30 ` bugzilla at busybox.net
2019-09-20 15:09 ` bugzilla at busybox.net
2019-09-20 20:51 ` bugzilla at busybox.net
2019-09-23 12:20 ` bugzilla at busybox.net
2019-09-25 20:09 ` bugzilla at busybox.net

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-all 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=bug-12241-163-eDx6bGsXG7@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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