Bug 9416 - Running on 2016.11-rc1 second make fails "makedevs: line 23: Couldnt create node /buildroot-2016.11-rc1/output/target/dev/console: File exists"
Summary: Running on 2016.11-rc1 second make fails "makedevs: line 23: Couldnt create n...
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-10 09:10 UTC by Sven Norinder
Modified: 2016-12-07 15:06 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Norinder 2016-11-10 09:10:32 UTC 

    


    


      



        
          Comment 1
        

        
          Yann E. MORIN

        

        
        

        
          2016-11-10 09:14:57 UTC
        

      






Sven,

Thanks for the report, but this has already been fixed with commit c85cd18 (makedevs: make device node creation idempotent).

Regards,
Yann E. MORIN.

    


    


      



        
          Comment 2
        

        
          Andy Shevchenko

        

        
        

        
          2016-12-01 14:23:02 UTC
        

      






Have another message, what did I miss?

makedevs: line 24: node ...output/target/dev/console exists but is of wrong file type
fs/cpio/cpio.mk:42: recipe for target '...output/images/rootfs.cpio' failed

93106e9 Update for 2016.11-rc3

    


    


      



        
          Comment 3
        

        
          Peter Korsgaard

        

        
        

        
          2016-12-01 18:02:12 UTC
        

      






Is this with a clean tree? We have reworked the makedevs handling between rc1 and rc3 (and final 2016.11), so moving between rc1 and rc3 without doing a make clean in between is bound to give problems.

Can you verify with a clean build on latest (E.G. 2016.11) if it still happens for you? Thanks

    


    


      



        
          Comment 4
        

        
          Sven Norinder

        

        
        

        
          2016-12-02 09:16:42 UTC
        

      






No problems noted with 2016.11.
Thank you.
/Sven

    


    


      



        
          Comment 5
        

        
          Peter Korsgaard

        

        
        

        
          2016-12-02 10:04:25 UTC
        

      






Great, I will mark it as resolved then

    


    


      



        
          Comment 6
        

        
          Andy Shevchenko

        

        
        

        
          2016-12-07 15:06:29 UTC
        

      






(In reply to Peter Korsgaard from comment #3)
Yeah, that was the issue. Sorry for a noise.