Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 173675 - sci-libs/blas-atlas-3.7.30 doesn't compile on PPC
Summary: sci-libs/blas-atlas-3.7.30 doesn't compile on PPC
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC Linux
: High normal (vote)
Assignee: Gentoo Science Related Packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-07 16:43 UTC by Dave
Modified: 2007-04-24 01:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,100.61 KB, text/plain)
2007-04-07 16:44 UTC, Dave
Details
emerge --info (info,8.15 KB, text/plain)
2007-04-07 16:44 UTC, Dave
Details
New build.log (new build.log,100.61 KB, text/plain)
2007-04-20 23:18 UTC, Dave
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave 2007-04-07 16:43:47 UTC
See attachments
Comment 1 Dave 2007-04-07 16:44:28 UTC
Created attachment 115673 [details]
build.log
Comment 2 Dave 2007-04-07 16:44:48 UTC
Created attachment 115674 [details]
emerge --info
Comment 3 Joe Jezak (RETIRED) gentoo-dev 2007-04-08 00:57:42 UTC
It seems that blas-atlas isn't properly detecting your CPU.  Do any versions work?

sci team: Is there anything we can do about this?  Auto-detecting CPUs is kind of bad (I can't compile for a G3 on my G4, it always turns on Altivec).
Comment 4 Dave 2007-04-08 02:26:46 UTC
I have 3.7.24 installed
Comment 5 Markus Dittrich (RETIRED) gentoo-dev 2007-04-09 14:07:59 UTC
Hi Dave,

Could you please try the patch I posted at bug #172583 !

@Joe: Unfortunately, CPU detection and tuning is an integral part
of blas-atlas optimization routine so I don't think there is anything
we can do apart from filing bugs upstream. The main atlas developer
is very resposive. 

cheers,
Markus
Comment 6 Christophe Philemotte 2007-04-13 07:36:12 UTC
I've got the same error ong my ppc and I've tried the patch from #172583.

The MACRO error is corrected, and now the package compiles.

Thanks Markus
Christophe

(In reply to comment #5)
> Hi Dave,
> 
> Could you please try the patch I posted at bug #172583 !
> 
> @Joe: Unfortunately, CPU detection and tuning is an integral part
> of blas-atlas optimization routine so I don't think there is anything
> we can do apart from filing bugs upstream. The main atlas developer
> is very resposive. 
> 
> cheers,
> Markus
> 

Comment 7 Markus Dittrich (RETIRED) gentoo-dev 2007-04-13 12:33:08 UTC
Hi Christophe,

Thank you very much for testing and I am glad the patch works.
As soon as Dave gives me his "thumbs-up" I'll apply the patch to portage.

Cheers,
Markus
Comment 8 Dave 2007-04-15 02:28:09 UTC
I get this error now:
  STAGE 2-1-2: CacheEdge DETECTION


   STAGE 2-1-3: LARGE/SMALL CASE CROSSOVER DETECTION


   STAGE 2-1-4: LEVEL 3 BLAS TUNE
make -f Makefile INSTALL_LOG/atlas_dtrsmXover.h pre=d 2>&1 | ./xatlas_tee INSTALL_LOG/dL3TUNE.LOG
make -f Makefile dcblaslib 2>&1 | ./xatlas_tee INSTALL_LOG/dL3TUNE.LOG
      done.


   STAGE 2-1-5: GEMV TUNE
make -f Makefile INSTALL_LOG/dMVRES pre=d 2>&1 | ./xatlas_tee INSTALL_LOG/dMVTUNE.LOG
make[1]: *** [build] Error 255
make[1]: Leaving directory `/var/tmp/portage/sci-libs/blas-atlas-3.7.30/work/ATLAS/gentoo-build'
make: *** [build] Error 2

!!! ERROR: sci-libs/blas-atlas-3.7.30 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  blas-atlas-3.7.30.ebuild, line 101:   Called die

!!! make failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sci-libs/blas-atlas-3.7.30/temp/build.log
Comment 9 Markus Dittrich (RETIRED) gentoo-dev 2007-04-17 23:31:34 UTC
Hi Dave,

Unfortunately, your output doesn't tell me what went wrong.
Is there any chance you can post your complete emerge log 
up to the error somewhere?

Thanks,
Markus
Comment 10 Dave 2007-04-20 23:17:31 UTC
Sorry about that.  I'm creating a new attachment
Comment 11 Dave 2007-04-20 23:18:03 UTC
Created attachment 116866 [details]
New build.log
Comment 12 Markus Dittrich (RETIRED) gentoo-dev 2007-04-21 11:59:45 UTC
(In reply to comment #11)
> Created an attachment (id=116866) [edit]
> New build.log
> 

Hi Dave,

Thanks :) 
You are getting the same error reported initially AFAICT. Your output
doesn't show that you are actually applying the patch posted in
bug #172583! Are you sure that you did this, otherwise the problem
will of course persist.

Thanks,
Markus
Comment 13 Dave 2007-04-22 13:55:10 UTC
(In reply to comment #12)
> (In reply to comment #11)
> > Created an attachment (id=116866) [edit]
> > New build.log
> > 
> 
> Hi Dave,
> 
> Thanks :) 
> You are getting the same error reported initially AFAICT. Your output
> doesn't show that you are actually applying the patch posted in
> bug #172583! Are you sure that you did this, otherwise the problem
> will of course persist.
> 
> Thanks,
> Markus
> 

Sorry about that.  Attached the wrong file.  But I did apply the patch, and this time it worked.  Last time it didn't for some odd reason.  I did do a kernel upgrade and reboot since then.

Comment 14 Markus Dittrich (RETIRED) gentoo-dev 2007-04-24 01:44:39 UTC
Hi Dave,

I am glad it works. I just applied the patch to the ebuild in
portage cvs.

Thanks,
Markus