Bug 18728 - 6_s1: libgcj_bc.so libgcj.so libgcj-tools.so libgij.so dangling links
Summary: 6_s1: libgcj_bc.so libgcj.so libgcj-tools.so libgij.so dangling links
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-18 01:12 CEST by Bit Twister
Modified: 2017-01-24 09:24 CET (History)
1 user (show)

See Also:
Source RPM: gcc-5.4.0-1.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-06-18 01:12:15 CEST 
Description of problem:

The following are the dangling links: 
/usr/lib/gcc/x86_64-mageia-linux-gnu/5.4.0/32/libgcj_bc.so -> ../../../i586-mageia-linux-gnu/5.4.0/libgcj_bc.so 
/usr/lib/gcc/x86_64-mageia-linux-gnu/5.4.0/32/libgcj.so -> ../../../i586-mageia-linux-gnu/5.4.0/libgcj.so 
/usr/lib/gcc/x86_64-mageia-linux-gnu/5.4.0/32/libgcj-tools.so -> ../../../i586-mageia-linux-gnu/5.4.0/libgcj-tools.so 
/usr/lib/gcc/x86_64-mageia-linux-gnu/5.4.0/32/libgij.so -> ../../../i586-mageia-linux-gnu/5.4.0/libgij.so 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Clean install of Mageia-6-x86_64-NETWORK-install 
   with enabled non-free and tainted media in a VirtualBox guest.
7. click up a terminal
8. su - root
9. urpmi symlinks
10. apply all updates, then run
11. symlinks -r / | grep dangling
Comment 1 Bit Twister 2016-06-18 01:17:04 CEST 
Missed a link
/usr/lib64/gcc-lib/x86_64-mageia-linux-gnu/3.3.6/32/libstdc++.so -> ../../../../32/libstdc++.so.5.0.7 

Not sure but my bug report generator suggests that maybe that came from gcc3.3-3.3.6-14.mga6.src.rpm
Marja Van Waes 2016-06-18 12:25:55 CEST

CC: (none) => marja11
Assignee: bugsquad => tmb

Marja Van Waes 2016-08-29 16:59:32 CEST

Assignee: tmb => basesystem

Comment 2 Bit Twister 2017-01-24 09:24:39 CET 
problem no longer exists.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.