SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just FYI folks, I tried building 4.19 for i686 in an up-to-date -current VM multiple times, but it died (repeatably) with the old gcc favourite: "internal compiler error: Segmentation fault". So there won't be a 32-bit 4.19 dusk kernel for the foreseeable future. Sorry!
How did you get to the conclusion that is the problematic commit? Maybe I am missing something obvious, but to me it looks like it removes support for old gcc versions which shouldn't affect current?
How did you get to the conclusion that is the problematic commit? Maybe I am missing something obvious, but to me it looks like it removes support for old gcc versions which shouldn't affect current?
And I quote!!! Reverse the affect by adding it back since it didn't compile on the Newer or whatever version. Some are just too smart for their own good!!!
Last edited by PROBLEMCHYLD; 10-22-2018 at 06:31 PM.
And I quote!!! Reverse the affect by adding it back since it didn't compile on the Newer or whatever version. Some are just too smart for their own good!!!
At the risk of also being too smart for my own good, why would a commit removing support for gcc version < 4.6 have any bearing on Slackware -current?
What are you even talking about? The subject was Linux 4.19 failing to build on -current 32 bit.
Because I use his builds and I'm not on current. What don't you understand, if it not building on current or whatever, lets find a solution. Reverting is a possibility.
Last edited by PROBLEMCHYLD; 10-22-2018 at 06:51 PM.
So, stop trying to respond to every post to get likes and count up.
I responded to your post to try to get you to clarify what you meant, since the commit you referenced obviously has nothing to do with the issue that was being discussed. You then made it abundantly clear that you have no idea what you are talking about, so I tried to exit the conversation without making a big deal about that. But now that you've decided to act like a jerk instead of actually explaining yourself, there you have it. Bye.
I responded to your post to try to get you to clarify what you meant, since the commit you referenced obviously has nothing to do with the issue that was being discussed. You then made it abundantly clear that you have no idea what you are talking about, so I tried to exit the conversation without making a big deal about that. But now that you've decided to act like a jerk instead of actually explaining yourself, there you have it. Bye.
And yet you took a half-hour to come up with a rebuttal. You need a life, I hope you get one. Don't focus on me because I'm not a threat, but I can easily become one.
Last edited by PROBLEMCHYLD; 10-22-2018 at 07:43 PM.
And yet you took a half-hour to come up with a rebuttal. You need a life, I hope you get one.
ROFL. I have no life because I'm not on the forums constantly. That makes about an much sense as anything else you've posted today. Enjoy being the only person on my ignore list.
ROFL. I have no life because I'm not on the forums constantly. That makes about an much sense as anything else you've posted today. Enjoy being the only person on my ignore list.
I have never quoted or contacted you personally, so I won't lose any sleep tonight. Lol, You can use your tactics on something or someone who cares about getting banned. I'll continue making it with or without LQ. I have done it majority of my life. You might need them because of your insecurities, but I don't....My wife and kids will be just fine and so will I.
Last edited by PROBLEMCHYLD; 10-22-2018 at 08:13 PM.
Because I use his builds and I'm not on current. What don't you understand, if it not building on current or whatever, lets find a solution. Reverting is a possibility.
I'm just curious, what are you using? Slackware 14.2 has gcc-5.3.0, Slackware 14.1 has gcc-4.8.2 and Slackware 14.0 has gcc-4.7.1 so I think it would not matter for any supported Slackware release? I'm also not sure this issue would present itself with any of the older gcc versions shipped in Slackware releases, have you tried building the kernel yourself?
As for finding a solution, I think the best method would be to git bisect the kernel and find the commit that caused the issue, but that also seems very tedious...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
