This is the mail archive of the mailing list for the crossgcc project.

See crosstool-NG for lots more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Problem with installing C library

Dear crosstool developers,

I have got tricky problem during building of crosstool-ng-1.18:

I build crosstool-ng in virtual machine on linux distribution Ubuntu
12.04 LTS. Mostly of builds are successfully,
but from time to time the compilation fail during building of libc
part. I have configured glibc-2.17.

If I look to the log file I find there this:

[ERROR]    collect2: error: ld returned 1 exit status
[ERROR]    make[3]: ***
Error 1
[ALL  ]    make[3]: Leaving directory
[ERROR]    make[2]: *** [elf/subdir_lib] Error 2
[ALL  ]    make[2]: Leaving directory
[ERROR]    make[1]: *** [all] Error 2
[ALL  ]    make[1]: Leaving directory
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing C library'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR]  >>        called from:
[ERROR]  >>        called from:
[ERROR]  >>        called from:
[ERROR]  >>        called from: main[scripts/]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>
'/home/kistler/svn/060_Build/maXYmoNC/crosstool-ng-1.18.0/docs/B -
Known issues.txt'

If I tried to analyze this problem and I found some strange behavior
before error occurred.
I try to describe it:
1. Problem seems to be during execute script Makerules
(./crosstool-ng/targets/src/glibc-2.17/Makerules) which edit
2. In this Makerules script in line 470 is called command 'sed' (see
lines below)

465: $(common-objpfx) $(common-objpfx)config.make $(..)Makerules
466:    $(LINK.o) -shared -Wl,-O1 \
467:          -nostdlib -nostartfiles \
468:          $(sysdep-LDFLAGS) $(config-LDFLAGS) $( \
469:          -Wl,--verbose 2>&1 | \
470:      sed > $@T \

When my build failed and I look to the build.log file I can see small
differences in parameters of this 'sed'.
See differences between successfully build and failed build:
Successfully build: ...... PROVIDE(__start___libc_subfreeres = .);
__libc_subfreeres : { *(__libc_subfreeres) } ......... parameters are
same like in script Makerules
Failed build:          ...... PROVIDE(__start___libc_subfreeres = .);
__libc_subfreeres : { __libcbc_subfreeres) } ......... parameters are
corrupted (*, bracket are missing)

In my point of view this corruption in output file shlib.ldsT failed my build.

Do you have any idea what is wrong ?
In this link you can download whole build.log file:

Best regardes, Zdenko Bacik.

For unsubscribe information see

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]