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.
As one who has been on the internet since '91, using linux since 92/93 (too far back for an old fella like me to remember) and who has contributed to many projects in the past, I've learned just because someone can contribute and be usually helpful, does not mean to say they can also not be full of themselves.
I couldnt care less if I was on his ignore list, if he is so thin skinned, so be it, he has treated me with contempt in hte past so thats how I see him.
Now back to ON TOPIC, I can report that it *IS* slackwares install of ffmpeg thats at fault.
I reneged, swearing that my basic-purpose-only headless home machines will only use official packages - I removed ffmpeg, got the source and built it myself, and minidlna built right away.
thats really funny Eric, because I thought *I WAS REPORTING A POSSIBLE PROBLEM*
get off your damn high an mighty horse. If you cant contribute to the issue at hand constructivly, then dont.
Just like your ext4 quota comment, absolutely useless, your either trying to imporve your post count, dont bother actually reading whats posted, or your just trolling
OK let's kill it dead then. I downloaded the minidlna sources, ran ./configure && make and what do you think... no errors. So what did you miss after 21 years of being l33t my dear Nob?
You showed a part of the 'config.log' file but you did not show the relevant bits. Let's share a grep on 'libavformat' out of the configure output that I captured:
Code:
checking libavformat/avformat.h usability... yes
checking libavformat/avformat.h presence... yes
checking for libavformat/avformat.h... yeschecking ffmpeg/libavformat/avformat.h usability... no
checking ffmpeg/libavformat/avformat.h presence... no
checking for ffmpeg/libavformat/avformat.h... no
checking libav/libavformat/avformat.h usability... no
checking libav/libavformat/avformat.h presence... no
checking for libav/libavformat/avformat.h... no
checking avformat.h usability... no
checking avformat.h presence... no
checking for avformat.h... no
checking ffmpeg/avformat.h usability... no
checking ffmpeg/avformat.h presence... no
checking for ffmpeg/avformat.h... no
checking libav/avformat.h usability... no
checking libav/avformat.h presence... no
checking for libav/avformat.h... no
checking for avformat_open_input in -lavformat -lavcodec -lavutil -lz... yes
You see that the header was actually already found BEFORE that part of logfile you shared with us. And why is that? It is because a configure script is relentless and will plow through all the options it has been given, reporting what it finds and recording a success for later use. Here, success was right at the first probe but the script continues anyway.
It's caused by this line in the configure script:
Code:
for ac_header in libavformat/avformat.h ffmpeg/libavformat/avformat.h libav/libavformat/avformat.h avformat.h ffmpeg/avformat.h libav/avformat.h
So, again, your post was OFF-TOPIC in this thread since it is neither about a bug in Slackware's ffmpeg nor a request to add minidlna to Slackware. Your post is nothing but a display of your failure to interpret what you see when you try to compile something from source.
The fact that you accuse me of trolling only shows your ignorance and social failure.
Wed Dec 9 21:10:40 UTC 2020
kde/powerdevil-5.20.4-x86_64-2.txz: Rebuilt.
Moved 10-enable-powerdevil-discrete-gpu.rules.new to
/usr/share/polkit-1/rules.d/. Thanks to Robby Workman.
Moved 10-enable-session-power.rules to the elogind package.
Moved 10-enable-upower-suspend.rules to the upower package.
Thanks to GazL.
It seems that doinst.sh is still trying to use the old path /etc/polkit-1/rules.d/ instead of /usr/share/polkit-1/rules.d/.
Edit: Sorted the update, just have to give it another go. See if it'll work now.
Thank you Pat!
Edit2: A Bit closer, I do get logged in, but still denied access to the google drive (if I open a new tab and enter gmail for example, I am logged in).
Nothing odd related to this found in any log file (that I find)
Edit3: Found the reason why it's not working...
It's missing kaccounts-integration and kaccounts-providers
From slackware64-current/source/kde/kde/modules/applications:
# Not currently packaging due to deps needed for kaccounts-integration, and
# more deps needed for those deps. Might check into it again later...
#kaccounts-integration
#kaccounts-providers
Last edited by MDKDIO; 12-15-2020 at 03:07 PM.
Reason: Edit3 part added...
It would be very great if openjdk was added to slackware. Should it be openjdk 8 or openjdk 11? Which one should it be?
I'll second that. I've installed it since JDK is an Arduino IDE dependency. On 14.2, I've replaced JDK with OpenJDK. I've run into no issues. (On 14.2, I installed the "arduino" IDE Slackbuild, the one that has only JDK as a dependency, not the "Arduino" Slackbuild.)
With that said, once again AlienBob has been good enough to provide OpenJDK 7 and 8 here
And if ppr:kut happens to see this, I emailed you a patch for the ffmpeg on SBo to do the same thing. Hopefully this will be something you'll consider implementing.
I really thought I replied to this already, but checking my mails I see I obviously did not
Sorry about that! I'll send a reply to the mail there, but for folks reading here:
I don't think it's the SlackBuild's job to do this. I understand why you'd want this, and I appreciate the effort that went into the patch, but that's more or less turning the SlackBuild into a build system for ffmpeg.
The effort would be better served patching ffmpeg's configure to do this instead and try to get it upstream. If they reject it, based on the reasoning given, we can decide how to proceed on our side.
I got a bug with xfce terminal, might also apply to the other terminals. But in xfce if the screen goes black like it should after a period of inactivity and I move the mouse to awaken the computer again, the xfce terminal stops working. Anyone else getting this bug?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.