From: bc20 on 9 Sep 2009 15:16 On Wed, 09 Sep 2009 19:09:54 +0000, bc20 wrote: > On Wed, 09 Sep 2009 19:04:05 +0000, bc20 wrote: > >> On Wed, 09 Sep 2009 15:24:36 +0000, bc20 wrote: >> >> >> F$@! Doing that broke my sh$! >> >> I can't even do a simple slackbuild now. >> >> "C compiler cannot create executables" >> >> What kind of BS is this? > > Example: > > (xbill, first stupid little program that came to mind to use as example) > ) > # ./xbill.SlackBuild > > [everything extracts ok] > > checking for gcc... gcc > checking whether the C compiler (gcc -O2 -march=i486 -mtune=i686 ) > works... no > configure: error: installation or configuration problem: C compiler > cannot create executables. Nevermind. I'm just stupid. I forgot to set the arch variable to x86_64 It works. Bill is running around stealing OS's...
From: Peter Chant on 9 Sep 2009 19:16 bc20 wrote: > I was planning on staying "pure 64", but there are too many 32bit > programs that I want to compile and run, so I caved in and added 32bit > support. > > Everyone else finding themselves doing the same? > > http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib Simple choice for me. Bin perfectly good printer or go multilib. Pete -- http://www.petezilla.co.uk
From: bc20 on 9 Sep 2009 19:55 On Thu, 10 Sep 2009 00:16:56 +0100, Peter Chant wrote: > bc20 wrote: > >> I was planning on staying "pure 64", but there are too many 32bit >> programs that I want to compile and run, so I caved in and added 32bit >> support. >> >> Everyone else finding themselves doing the same? >> >> http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib > > Simple choice for me. Bin perfectly good printer or go multilib. > > Pete I hear you. For me it was Skype as I have friends in Europe and Argentina. (Figured out the other thing with the Makefile. It was a GCC version issue.)
From: Peter Chant on 17 Sep 2009 17:40 bc20 wrote: > > I hear you. For me it was Skype as I have friends in Europe and > Argentina. > > (Figured out the other thing with the Makefile. It was a GCC version > issue.) Though I may be biased by limited use the seamless way Slamd64 handled 32 and 64 applications at once was impressive. OTOH I see the logic in going for a pure 64 bit system. Pete -- http://www.petezilla.co.uk
First
|
Prev
|
Pages: 1 2 Prev: Virtualbox compile errors on Slack 13.0 64? Next: Corporate creep in Linux? (mini-rantette) |