LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-05-2012, 05:29 AM   #286
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,357
Blog Entries: 2

Rep: Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979

Quote:
Originally Posted by slackbat View Post
For starters I am a realist.
May be. But as a realist you should check your facts first, before jumping to conclusions.

Quote:
Look at the actions
We have. May be you try it yourself: http://slackware.osuosl.org/slackwar.../ChangeLog.txt
Looks like enough action.

Quote:
The site is still down. The second period that the site has been down. This is one thing we know.
Instead of whining about a website that is down and jumping to conclusions: Again, check your facts. You should have read this thread and the explanations in it.

Quote:
But again still no new release - another action/thing we know.
Again, you haven't checked your facts: What we know is that there are currently major changes in -current. What we also know is that Pat releases a new version only when it is well tested. And also that Slackware has no fixed release schedule.
These are the facts. Where do they imply that Slackware is dying?

Quote:
Its strange that anyone who shows any form of realism is immediately labelled a troll or something.
Nothing strange with that. You didn't check your facts, so you really can't be a realist. People that are spreading FUD without any base are normally called trolls.

See it as that: If you want a distro where every change is announced in literally dozens of blogs and that has a fixed release cycle then go for Ubuntu or Fedora. We Slackers prefer well tested and stable systems and don't care about marketing messages in blogs. Changelog.txt is enough information.

Now back to syncing my mirror and upgrading my systems.

Last edited by TobiSGD; 05-05-2012 at 11:33 AM. Reason: fixed typing
 
2 members found this post helpful.
Old 05-05-2012, 05:53 AM   #287
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
Quote:
Originally Posted by GazL View Post
Actually, other than the missing libffi.pc pkg-config file from the gcc-java package, all the version bumps needed to run the new gimp version went on cleanly using the existing slackbuild scripts in current.
You can install libffi from slackbuilds which will give you a usable version of the library. The version included in gcc is for gcc to use, not for external use.

I see in the other thread you complain about the location of the include file, this is by design and not an error.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23935
 
Old 05-05-2012, 06:08 AM   #288
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,524
Blog Entries: 1

Rep: Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997Reputation: 997
Quote:
Originally Posted by slackbat View Post
For starters I am a realist. Also words can lie. Look at the actions - dont listen to what is said by those developers and slacklfanbois.
Yes, actions speak louder than words. We've got a huge batch of updates in -current. I've upgraded this morning and am running a very stable system. What more would I want? I don't know how much you know about Slackware, but please note that Slackware -current is not eg. Fedora-rawhide where updates are much frequent but most often break things so running Fedora-rawhide is REALLY for brave people. For the record, I have nothing against Fedora. They just have a different testing model than that of Slackware. Here Pat and the rest of the crew do the initial testing and only then give us the opportunity to do further testing.

Quote:
Originally Posted by slackbat View Post
What are the actions. The site is still down. The second period that the site has been down. This is one thing we know.
So what? Slackware website is not the Slackware operating system. Slackware does not run a marketing campaign that would rely on their website. The way new users learn about slackware is different than that of eg. Ubuntu (where their website is full of marketing slogans and trendy buzz words. Slackware doesn't rely on its websites (it's the mirrors that count). I admit it's not an ideal thing that the website is down, but it's not the end of the world.

Quote:
Originally Posted by slackbat View Post
Slackware is - or was - a good distro. But again still no new release - another action/thing we know.
No new release?! Well, sorry to break it to you but Slackware is not Fedora/Ubuntu where releases are frequent and scheduled. Don't like the release model, change your distro and stop spreading crap.

Quote:
Originally Posted by slackbat View Post
Its strange that anyone who shows any form of realism is immediately labelled a troll or something. Its so easy to reject what we dont like to hear in a convenient package. Life is not that simple so get over yourself. Should I call you a troll for practically calling me a troll??
If you expect a "Pat" on the back for spreading nonsense, I'm afraid that's a wrong forum. YOU get over it.

Last edited by sycamorex; 05-05-2012 at 06:09 AM.
 
2 members found this post helpful.
Old 05-05-2012, 08:34 AM   #289
linq
Member
 
Registered: May 2010
Location: Russia
Distribution: Slackware 1.0,...64-14.1
Posts: 32

Rep: Reputation: 2
Quote:
Originally Posted by ponce View Post
I suspect that you are not familiar with slackware or you should know that "it's ready when it's ready".
And I'm a slacker from, I believe, version 0.9something. And I love Slackware. There's only one thing about Slackware, I actually hate - it's this "it's ready when it's ready".
 
Old 05-05-2012, 08:38 AM   #290
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,357
Blog Entries: 2

Rep: Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979Reputation: 3979
Quote:
Originally Posted by linq View Post
And I'm a slacker from, I believe, version 0.9something. And I love Slackware. There's only one thing about Slackware, I actually hate - it's this "it's ready when it's ready".
Simple fix: Run Slackware -current instead (but be aware, -current is never ready) if you want to have newer software, or go to a distro like Ubuntu when you rather want to have a fixed release cycle than a stable system.
 
Old 05-05-2012, 08:46 AM   #291
GazL
Senior Member
 
Registered: May 2008
Posts: 3,312

Rep: Reputation: Disabled
Quote:
Originally Posted by wildwizard View Post
You can install libffi from slackbuilds which will give you a usable version of the library. The version included in gcc is for gcc to use, not for external use.

I see in the other thread you complain about the location of the include file, this is by design and not an error.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23935
I never said it was an error, just that I didn't understand why they were in such a strange place.

Anyway, Thanks for the link Wildwiz. I now see that having the ffi include files in /usr/include would be a problem if there is a need to support the concurrent installation of multiple versions of gcc each with their own version of libffi, so that explains why they did that with the includes.

However the introduction of a libffi package on Slackware introduces a collision with the contents of the gcc-java package: specifically the /usr/lib${LIBDIRSUFFIX}/libffi* files. Having package installation order become significant is something I don't like and try and avoid wherever possible. This is why I thought of manually adding a libffi.pc file and using the libffi that was shipped with gcc as the system-wide libffi. And it seemed to work ok. Is there actually any problem with doing it this way?

Last edited by GazL; 05-05-2012 at 08:48 AM.
 
Old 05-05-2012, 10:01 AM   #292
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,380

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
@GazL: after your hint of simply creating the pkgconfig file I've done the same and no prob so far

Last edited by ponce; 05-05-2012 at 10:08 AM.
 
Old 05-05-2012, 12:45 PM   #293
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,906

Rep: Reputation: Disabled
Quote:
Originally Posted by wildwizard View Post
You can install libffi from slackbuilds which will give you a usable version of the library. The version included in gcc is for gcc to use, not for external use.

I see in the other thread you complain about the location of the include file, this is by design and not an error.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23935
All of the libffi files shipped in the gcc-java package should be removed before compiling anything that links libffi, or else you will get some binaries that link both libffi.so.4 (shipped with gcc-java) and libffi.so.whatever is in the standalone package (3.0.10 ships libffi.so.5 while 3.0.11 ships libffi.so.6 - I hope every release doesn't bump soversion).

As I stated in another thread, gcj links libffi statically, so there's absolutely no reason for the libffi stuff to be included in gcc-java at all, and we'll get that fixed before it's relevant for the distribution as a whole

---------- Post added May 5th, 2012 at 12:46 ----------

Quote:
Originally Posted by ponce View Post
@GazL: after your hint of simply creating the pkgconfig file I've done the same and no prob so far
Will glib2-2.32.x build that way too? It wouldn't for me, but even if it will, I still think the better solution is to ship standalone libffi and kill the libffi stuff in gcc-java.
 
2 members found this post helpful.
Old 05-05-2012, 01:04 PM   #294
GazL
Senior Member
 
Registered: May 2008
Posts: 3,312

Rep: Reputation: Disabled
Quote:
Originally Posted by rworkman View Post
All of the libffi files shipped in the gcc-java package should be removed before compiling anything that links libffi, or else you will get some binaries that link both libffi.so.4 (shipped with gcc-java) and libffi.so.whatever is in the standalone package (3.0.10 ships libffi.so.5 while 3.0.11 ships libffi.so.6 - I hope every release doesn't bump soversion).

As I stated in another thread, gcj links libffi statically, so there's absolutely no reason for the libffi stuff to be included in gcc-java at all, and we'll get that fixed before it's relevant for the distribution as a whole

---------- Post added May 5th, 2012 at 12:46 ----------



Will glib2-2.32.x build that way too? It wouldn't for me, but even if it will, I still think the better solution is to ship standalone libffi and kill the libffi stuff in gcc-java.
I didn't try 2.32, but 2.33.1 built just fine with the hacked together libffi.pc I posted in that other thread.

If the libffi libraries aren't needed by the gcc java stuff post build then I'm all for getting rid of them from the gcc-java package as you say and using the standalone libffi package. My main concern was the risk of unintentional downgrading/overwriting because they are in two different packages. The rest was just curiosity.

I did try rebuilding gcc at one point (after uninstalling gcc-java and installing libffi-3.0.11) adding --with-system-libffi to the configure, but it still resulted in the libffi.so.4 files being created, so that didn't work out (It was pretty much a shot in the dark though)


Thanks for posting Robby. Looks like you guys are on top of this one, so I'll leave it with you.

Last edited by GazL; 05-05-2012 at 01:07 PM.
 
Old 05-05-2012, 02:28 PM   #295
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,380

Rep: Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840Reputation: 840
Quote:
Originally Posted by rworkman View Post
Will glib2-2.32.x build that way too? It wouldn't for me, but even if it will, I still think the better solution is to ship standalone libffi and kill the libffi stuff in gcc-java.
yes, 2.32.2 built fine, but I'll switch to the standalone libffi, seems better to me too

to say the truth what puzzles me really is gobject-introspection yes/no
 
Old 05-05-2012, 03:40 PM   #296
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,906

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
yes, 2.32.2 built fine, but I'll switch to the standalone libffi, seems better to me too
Well, I wonder what I did to stuff up 2.32+ building, since it worked for you and Gazl. Oh well, the better approach is the one I ended up with anyway...

Quote:
to say the truth what puzzles me really is gobject-introspection yes/no
Well, for now, it's "no" - but gtk+3 is going to require that anyway, which will mean adding gobject-introspection and rebuilding/updating quite a few components to use it, and then building gtk+3. A lot of this stuff has been just shy of rabbit hole complexity...
 
1 members found this post helpful.
Old 05-05-2012, 04:57 PM   #297
audriusk
Member
 
Registered: Mar 2011
Location: Klaipėda, Lithuania
Distribution: Slackware
Posts: 231

Rep: Reputation: 102Reputation: 102
Quote:
Originally Posted by rworkman View Post
As I stated in another thread, gcj links libffi statically, so there's absolutely no reason for the libffi stuff to be included in gcc-java at all, and we'll get that fixed before it's relevant for the distribution as a whole
Glad to hear that libffi issue is going to be solved, as it concerns the project I'm interested in, PyPy, and many more as we can see from recent posts about libffi. Thanks.
 
Old 05-05-2012, 06:34 PM   #298
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,493

Rep: Reputation: 403Reputation: 403Reputation: 403Reputation: 403Reputation: 403
Quote:
Originally Posted by rworkman View Post
Well, I wonder what I did to stuff up 2.32+ building, since it worked for you and Gazl. Oh well, the better approach is the one I ended up with anyway...



Well, for now, it's "no" - but gtk+3 is going to require that anyway, which will mean adding gobject-introspection and rebuilding/updating quite a few components to use it, and then building gtk+3. A lot of this stuff has been just shy of rabbit hole complexity...
Yeah, i have tried building gtk+3 and it does requires gobject-instrospection and many other components
here are the requirements:
- gobject-introspection 1.32.1 (Available on SBo)
- pango-1.30
- gdk-pixbuf 2.26.1
- atk-2.4.0
- glib2-2.32.1
- libffi-3.0.11 (Available on SBo)

You can check my GTK+3 SlackBuild from my SlackHacks repository. It's adapted from Slackware's SlackBuild script
 
Old 05-06-2012, 10:41 AM   #299
foka
LQ Newbie
 
Registered: May 2012
Distribution: Slackware
Posts: 2

Rep: Reputation: Disabled
The Slackware site is down again?

The site of Slackware has been down AGAIN... (at least at this moment when I write this).

What is happening?

Last edited by foka; 05-06-2012 at 12:00 PM. Reason: Bad conclusions.....
 
Old 05-06-2012, 10:49 AM   #300
camorri
Senior Member
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.0 + 14.1
Posts: 4,828

Rep: Reputation: 431Reputation: 431Reputation: 431Reputation: 431Reputation: 431
Please take the time to read this link -->http://www.linuxquestions.org/questi...e-down-939712/

NO, Slackware is not dying. Stop spreading such fud.
 
2 members found this post helpful.
  


Reply

Tags
eric hameleers, patrick volkerding, slackware, www.slackware.com


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Where to find information about www.website.com/~username/ kenpeter Linux - Server 1 07-16-2009 08:26 AM
Can see website via fqdn but not through www SamuelHenderson Linux - Server 14 11-29-2007 11:49 AM
"www::mechanize"-->www.cpan.org using this module login to secure website vvnkishore Linux - General 0 10-04-2007 01:14 AM
New website http://www.lpi2b.com ve6hf` Linux - Certification 1 07-30-2005 05:56 PM


All times are GMT -5. The time now is 05:18 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration