Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 349580 - dev-lang/gdl-0.9 does not install /usr/bin/gdl
Summary: dev-lang/gdl-0.9 does not install /usr/bin/gdl
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Markus Dittrich (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-24 08:53 UTC by Christopher Dianthus
Modified: 2011-01-05 10:00 UTC (History)
1 user (show)

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


Attachments
build log dev-lang:gdl-0.9 (dev-lang:gdl-0.9:20101225-083232.log,192.18 KB, text/plain)
2010-12-25 09:10 UTC, Christopher Dianthus
Details
emerge --info on the system producing this odd result (emerge.info,4.64 KB, text/plain)
2010-12-25 09:13 UTC, Christopher Dianthus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Dianthus 2010-12-24 08:53:28 UTC
Hello,

I am not sure whether the e-build of a new version of dev-lang/gdl-0.9 produces correct install. The package compiles fine and installs fine, 


emerge -avp dev-lang/gdl
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild   R   ] dev-lang/gdl-0.9  USE="X fftw hdf hdf5 openmp python wxwidgets -grib -imagemagick -netcdf -udunits" 0 kB

but afterwards, the executable seem does not present. The binary package has ./bin durectory empty, and of course

[xxx@xxx]:~>gdl
gdl: Command not found.

It that intentional, or am I missing something? I apologize for possible misunderstanding.

Thank you in advance.





Reproducible: Always

Steps to Reproduce:
1. emerge the package
2. gdl
Comment 1 Mike Gilbert gentoo-dev 2010-12-25 00:01:56 UTC
Can you post emerge --info and attach a build log?

You can get portage to save the build log after a successful merge by setting PORT_LOGDIR in /etc/make.conf.
Comment 2 Christopher Dianthus 2010-12-25 09:10:07 UTC
Created attachment 258011 [details]
build log dev-lang:gdl-0.9

This is build log ofdev-lang:gdl-0.9  on x86 machine. The problem persists.
Comment 3 Christopher Dianthus 2010-12-25 09:13:12 UTC
Created attachment 258012 [details]
emerge --info on the system producing this odd result

This is output from emerge --info on the buggy (?) system producing this odd behaviour
Comment 4 Christopher Dianthus 2010-12-25 09:17:53 UTC
Hi Mike, 

I have attached the emerge logs and info.

I have still another problem on amd64 machine:

/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libantlr.a(ASTFactory.o): relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC
/usr/lib64/libantlr.a: could not read symbols: Bad value
collect2: ld returned 1 exit status

Perhaps this is another bug, but I am not opening it yet - it is likely due to some misconfiguration. I re-emerge libtool and libantlr, with no change.

Many thanks.

Dianthus
Comment 5 Christopher Dianthus 2010-12-25 09:19:02 UTC
(In reply to comment #4)
> Hi Mike, 
> 
> I have attached the emerge logs and info.
> 
> I have still another problem on amd64 machine:
> 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.4/../../../../x86_64-pc-linux-gnu/bin/ld:
> /usr/lib64/libantlr.a(ASTFactory.o): relocation R_X86_64_32 against `.bss' can
> not be used when making a shared object; recompile with -fPIC
> /usr/lib64/libantlr.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> 
> Perhaps this is another bug, but I am not opening it yet - it is likely due to
> some misconfiguration. I re-emerge libtool and libantlr, with no change.

It is still on the gdl 0.9, of course:

collect2: ld returned 1 exit status
make[3]: *** [libgdl.la] Error 1
make[3]: Leaving directory `/var/tmp/portage/dev-lang/gdl-0.9/work/gdl-0.9/src'
make[2]: *** [all-recursive] Error 1

Comment 6 Sébastien Fabbro (RETIRED) gentoo-dev 2011-01-04 05:05:24 UTC
should be fixed. thanks.
Comment 7 Christopher Dianthus 2011-01-05 10:00:00 UTC
Thank you, I have checked the new-ebuilds on a few machines, and now they work perfectly on both architectures (~x86 and ~amd64).

Many thanks.