Le 13 févr. 2014 à 23:28, Евгений Ростовцев a écrit : > But we changed a theme. What about broken libraries? > > http://git.altlinux.org/tasks/113911/build/100/x86_64/log > > Look at end of log.
I just fixed the linked libraries for the reported broken libraries, I'm not sure it's going to make the issues you are reporting go away, but it might help. For these frameworks, we were not passing GNUstep Make variables such as $(FND_LIBS) in LIBRARIES_DEPEND_UPON. As a side note, I strongly suggest that you don't attempt to create packages for modules disabled from the default build. For example, PaneKit or MediaKit. When you invoke 'make', you are also passing 'shared=yes', this seems like a bad idea to me. If we build some static libs during the build process, we don't want to turn them into shared libs. Moreoever GNUstep Make could intepret shared=yes in some unpredictable way, if the target is not a library or a framework. For eu-elflint failures, I don't know how to fix these: verify-elf: WARNING: ./usr/lib64/GNUstep/Frameworks/SystemConfig.framework/Versions/0/libSystemConfig.so.0.2: eu-elflint failed eu-elflint report failures for most libraries installed in /usr/lib on my Ubuntu system. I have never used eu-elflint, so I'm unsure how to intepret these results. If anybody knows how to interpret these and what could produce them, let me know… Could you give me the eu-elflint invocation, to know if any special flags are passed? Cheers, Quentin. _______________________________________________ Etoile-dev mailing list Etoile-dev@gna.org https://mail.gna.org/listinfo/etoile-dev
