Re: Strange linux-next build error

From: Daniel Hazelton <dhazelton@xxxxxxxxx>
Date: Sat, 3 May 2008 21:37:07 -0400

On Saturday 03 May 2008 18:40:18 Ingo Molnar wrote:

* Daniel Hazelton <dhazelton@xxxxxxxxx> wrote:

Can you try to do a:
make V=1 and post the output a few screen fulls before and until
the bug triggers.
They I will see if I can work out what is happening.

Thanks,
Sam

I've been unable to trigger it with "make V=1 bzImage" - does the
verbosity change, somehow, the default number of makes that get run ?

If it does, I could try adding -j2 or similar to see if that causes it
to trigger.

try something like:

make -j2 V=1 bzImage >log.txt 2>&1

and see whether the error shows up in log.txt. Console output caused by
the increased verbosity (especially if it's a slower console like an
xterm) can hide build races.

Ingo

And this appears to have been a false alarm. For the tests I did a clean pull
of the tree and started the build. When I kept *NOT* getting a build error on
the clean tree I started checking permissions and, while the files that this
error was happening for (and the containing directory) all had good
permissions, the correct ownerand all that - so I didn't look deeper. On
doing a deeper look it seems that there were some files and directories that
belonged to "root" and had 0644 for permissions.

After doing "make mrproper" and the reconfiguration I reset the owner/group on
the entire tree of files to be non-root and the build (at -j4) has finished
without a problem.

Sorry about that.

DRH

--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Follow-Ups:
- Re: Strange linux-next build error
  - From: Sam Ravnborg

References:
- Strange linux-next build error
  - From: Daniel Hazelton
- Re: Strange linux-next build error
  - From: Daniel Hazelton
- Re: Strange linux-next build error
  - From: Ingo Molnar

Prev by Date: Re: [Patch] (revised) net/xfrm/xfrm_policy.c: replace timer with delayed_work
Next by Date: Re: [Patch] (revised) net/xfrm/xfrm_policy.c: replace timer with delayed_work
Previous by thread: Re: Strange linux-next build error
Next by thread: Re: Strange linux-next build error
Index(es):
- Date
- Thread

Relevant Pages

Re: Strange linux-next build error
... the bug triggers. ... of the tree and started the build. ... permissions, the correct ownerand all that - so I didn't look deeper. ... So if you by accident have done "make bzImage" as root this ...
(Linux-Kernel)
Help! IE6 Registry Hacked
... The registry key tree permissions for HKCU\Software\Microsoft\Internet ... I know I can manually fix this by logging in as Admin, ... permissions, and then re-creating the tree, but this is quite painful. ...
(microsoft.public.windows.inetexplorer.ie6.browser)
Re: extended attributes
... Anyone know why vim behaves ... give it the appropriate ownership and permissions (and these ... "copy" one tree to another. ... on disk once: each file just appears twice, once in each tree ("it has ...
(Fedora)
Re: best dns config for new tree in forest
... Policies can be reset with DCGPOfix.exe ... Having to manage all the permissions and owership on existing ... tree to migrate all of my child domains into. ... If it is in a new forest there is only ONE way to setup AD Integrated DNS ...
(microsoft.public.windows.server.dns)
Re: directory permissions
... I have a directory tree for pictures and my users upload there pictures ... I have written a CGI script, who should be able to write some files to ... the directories of the tree and the files should be readable by browser. ... the directory should have 777 permissions to ...
(alt.linux)