List-MoreUtils-XS emerge fails

imesg · Guru Joined: 12 Jul 2002 Posts: 445

[Moderator note: the first three posts, and the post from eccerr0r encouraging a merge, were originally posted in one thread. All other posts up to and including my now-second post were in another thread. Per suggestion from eccerr0r, and considering that both of these seem to be related to calls to ld that ought to be calls to gcc, I merged the two threads. -Hu]

Trying to install gscan2pdf. It has a long list of dependencies. I got through about half or so.

fedeliallalinea · Posted: Wed Dec 06, 2017 7:13 am Post subject:

Your problem is

imesg · Guru Joined: 12 Jul 2002 Posts: 445

imesg · Guru Joined: 12 Jul 2002 Posts: 445

I have two almost identical laptops configured similarly and get to the same failure on each.

eccerr0r · Posted: Thu Jan 25, 2018 8:25 pm Post subject:

I think you got your LDFLAGS and CFLAGS mixed up. Ld does not take gcc options and gcc may not take ld options (it may pass stuff to the linker conditionally however).

Clear out your LDFLAGS and CFLAGS, especially remove gcc flags (like CFLAGS) from LDFLAGS, and ensure that works first.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

Hu · Moderator Joined: 06 Mar 2007 Posts: 21607

The emerge --info in the linked post agrees with eccerr0r's diagnosis. However, the current end of that thread contains a claim that the LDFLAGS have been set right. imesg, what are your current LDFLAGS for this package?

To elaborate slightly on eccerr0r's post, ld understands -O1. gcc understands -Wl,-O1 to be a request to pass -O1 to ld. You cannot pass -Wl,-O1 to ld directly.

imesg · Guru Joined: 12 Jul 2002 Posts: 445

krinn · Watchman Joined: 02 May 2003 Posts: 7470

LDFLAGS is set in your make.conf and if you wonder why that user from the link you gave has problem with them it's because this user has set LDFLAGS="${LDFLAGS} ${CFLAGS} -Wl,-flto" in his make.conf, which end up with his cflags pass to ld.

eccerr0r · Posted: Fri Jan 26, 2018 4:52 pm Post subject:

Again the suggestion is to totally get rid of extra CFLAGS/LDFLAGS that are written in your /etc/make.conf or /etc/portage/make.conf .
Then start adding them back and seeing which ones break things again and fix from there. Unless the other post has the wrong make.conf - this is all we can work with to figure out what's going on...

Perhaps we should get a mod to merge these threads ...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

imesg · Guru Joined: 12 Jul 2002 Posts: 445

eccerr0r · Posted: Fri Jan 26, 2018 7:00 pm Post subject:

Is it in your environment?

# echo $LDFLAGS

Did you set it in /etc/portage/bashrc?

You have set it somewhere, I can't think of it coming in manually and it's not the default setup... I'm not sure what the overlays do, I hope those didn't add this on somehow.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

eccerr0r · Posted: Fri Jan 26, 2018 11:38 pm Post subject:

Mods should merge https://forums.gentoo.org/viewtopic-t-1075912-highlight-.html - looks like the same problem.

Somehow you're still adding in bad LDFLAGS and CFLAGS.

If you have both LDFLAGS and CFLAGS completely unset or set to "" (empty) - portage should still work. Is this the case?

I don't believe that the LDFLAGS listed above is valid. Start with an empty one.

-pipe belongs in CFLAGS along with -O2 and -march=xxx. The linker is too late to choose most instructions and does not make sense to put those flags there.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

Hu · Moderator Joined: 06 Mar 2007 Posts: 21607

On my system, it appears it is default. I blanked /etc/portage/make.conf, then ran /usr/bin/env -i /usr/bin/emerge --info (so as not to have any environment variables that might affect it).

eccerr0r · Posted: Sat Jan 27, 2018 1:09 am Post subject:

Thanks for merge, was getting tedious to switch to the other page to reference :)

And ahhhh... I was tricked by a misnomer, that would be true that using gcc to link would require different command than using ld directly to link and hence that default really is a default if it's passed to gcc to do the linking.

Still odd that somehow the wrong flags are being passed to the linker causing it to fail.

Plus errors from configure that look like

imesg · Guru Joined: 12 Jul 2002 Posts: 445

eccerr0r · Posted: Sat Jan 27, 2018 6:17 pm Post subject:

Well see what happens if you unset the environment variable LD

Hu · Moderator Joined: 06 Mar 2007 Posts: 21607

That fits, and may also explain why this is limited to a few packages. Normally, setting $LD would not cause this:

imesg · Guru Joined: 12 Jul 2002 Posts: 445

imesg · Guru Joined: 12 Jul 2002 Posts: 445

This thread died. There is still not an answer other than unset LD. I still have the problem.

Thanks,

Hu · Moderator Joined: 06 Mar 2007 Posts: 21607

Unsetting LD in the running shells and removing it from your dotfiles is the answer. It is not normally set. We do not know where you set it. If you cannot find it via recursive grep, you could try using the shell's execution trace feature (set -x for a running shell; pass -x when starting a new one), but beware that this does not nest, so it might be turned off early.

imesg · Guru Joined: 12 Jul 2002 Posts: 445