[ERROR] Make won't run

[ERROR] Make won't run

[Nishka Dasgupta]

From: nishka.dasgupta_ug18@ashoka.edu.in

I can't run make because the process exits with error messages at various files. I reset all my changes, manually undid them, and fetched and rebased the origin again for good measure, but even now files that I haven't touched (from init to android to other files in the same directory) are causing the make process to exit with errors (usually an "Input/Output Error" in some .o file). I don't know what to do and would appreciate any assistance. (In case it helps, I was removing braces in a single line if statement on line 290 of drivers/staging/wilc1000/wilc_wfi_cfgoperations.c. Before that, Mr Kroah-Hartman had replied to an earlier commit pointing out that I had committed files that had no business being in this kernel, so I tried to roll back the commit with a git reset and then fetch the origin again.)

Thank you for your time.

Regards,
Nishka Dasgupta

Re: [Outreachy kernel] [ERROR] Make won't run

[Julia Lawall]

On Fri, 23 Feb 2018, Nishka Dasgupta wrote:

> From: nishka.dasgupta_ug18@ashoka.edu.in
>
> I can't run make because the process exits with error messages at
> various files. I reset all my changes, manually undid them, and fetched
> and rebased the origin again for good measure, but even now files that I
> haven't touched (from init to android to other files in the same
> directory) are causing the make process to exit with errors (usually an
> "Input/Output Error" in some .o file).

How much space do you have on your disk?  The kernel is big, and creating
.o files makes it even bigger.

> I don't know what to do and would
> appreciate any assistance. (In case it helps, I was removing braces in a
> single line if statement on line 290 of
> drivers/staging/wilc1000/wilc_wfi_cfgoperations.c. Before that, Mr
> Kroah-Hartman had replied to an earlier commit pointing out that I had
> committed files that had no business being in this kernel, so I tried to
> roll back the commit with a git reset and then fetch the origin again.)

If things are not going well with your git tree, you could just delete the
whole thing and clone it again.

julia

> Thank you for your time.
>
> Regards,
> Nishka Dasgupta
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/1519331234-14582-1-git-send-email-nishka.dasgupta_ug18%40ashoka.edu.in.
> For more options, visit https://groups.google.com/d/optout.
>

Re: [Outreachy kernel] [ERROR] Make won't run

[Greg KH]

On Fri, Feb 23, 2018 at 01:57:13AM +0530, Nishka Dasgupta wrote:
> From: nishka.dasgupta_ug18@ashoka.edu.in
> 
> I can't run make because the process exits with error messages at
> various files. I reset all my changes, manually undid them, and
> fetched and rebased the origin again for good measure, but even now
> files that I haven't touched (from init to android to other files in
> the same directory) are causing the make process to exit with errors
> (usually an "Input/Output Error" in some .o file). I don't know what
> to do and would appreciate any assistance. (In case it helps, I was
> removing braces in a single line if statement on line 290 of
> drivers/staging/wilc1000/wilc_wfi_cfgoperations.c. Before that, Mr
> Kroah-Hartman had replied to an earlier commit pointing out that I had
> committed files that had no business being in this kernel, so I tried
> to roll back the commit with a git reset and then fetch the origin
> again.)

Please provide the exact error messages, otherwise it's a bit hard to be
able to determine what is wrong with your kernel build.

And you have built a kernel successfully from the source tree before
modifying it, right?

thanks,

greg k-h

Error Disappeared

[Nishka Dasgupta]

I have now switched to native Linux. Everything appears to be working now. In answer to your question, I had successfully built a kernel from the source tree before trying the commands that led to this error. 
I apologise for the trouble.
Thanking you,
Nishka Dasgupta