[gentoo-user] glibc emerge error

[gentoo-user] glibc emerge error

[Corbin Bird]

Is anyone else having a sys-libs/glibc emerge compile failure?

> checking for python3... python3
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the environment variable
> *** and run configure again.
>  * ERROR: sys-libs/glibc-2.25-r10::gentoo failed (configure phase):
>  *   failed to configure glibc

sys-libs/glibc-2.25-r9 was set to masked / prompting this upgrade /
re-compile:

https://packages.gentoo.org/packages/sys-libs/glibc

Same error regardless of the version of glibc I attempt to emerge.

Corbin

Re: [gentoo-user] glibc emerge error

[Matthias Hanft]

Corbin Bird wrote:
> Is anyone else having a sys-libs/glibc emerge compile failure?
>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>> *** building glibc. Please change the environment variable
>> *** and run configure again.
> Same error regardless of the version of glibc I attempt to emerge.

Sure - this error always comes up here, too. Just enter

export LD_LIBRARY_PATH=

immediately before emerge, and it works.

-Matt

PS: And if you get some message concerning some variables which
    are too big (or something like that), enter
      mount -t tmpfs none /var/tmp/portage
    just before emerge (and "umount /var/tmp/portage" afterwards).
    I have to do this for the emerge of a few packages - I think
    it's because of my 17 TB filesystem.

Re: [gentoo-user] glibc emerge error

[Corbin Bird]

On 01/10/2018 12:22 PM, Matthias Hanft wrote:
> Corbin Bird wrote:
>> Is anyone else having a sys-libs/glibc emerge compile failure?
>>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>>> *** building glibc. Please change the environment variable
>>> *** and run configure again.
>> Same error regardless of the version of glibc I attempt to emerge.
> Sure - this error always comes up here, too. Just enter
>
> export LD_LIBRARY_PATH=
>
> immediately before emerge, and it works.
>
> -Matt
>
> PS: And if you get some message concerning some variables which
>     are too big (or something like that), enter
>       mount -t tmpfs none /var/tmp/portage
>     just before emerge (and "umount /var/tmp/portage" afterwards).
>     I have to do this for the emerge of a few packages - I think
>     it's because of my 17 TB filesystem.
>
>

Thanks, that fixed it.

Corbin

[gentoo-user] Re: glibc emerge error

[Nikos Chantziaras]

On 10/01/18 19:55, Corbin Bird wrote:
> Is anyone else having a sys-libs/glibc emerge compile failure?
> 
>> checking for python3... python3
>> checking LD_LIBRARY_PATH variable... contains current directory
>> configure: error:
>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>> *** building glibc. Please change the environment variable
>> *** and run configure again.
>>   * ERROR: sys-libs/glibc-2.25-r10::gentoo failed (configure phase):
>>   *   failed to configure glibc
> 
> sys-libs/glibc-2.25-r9 was set to masked / prompting this upgrade /
> re-compile:
> 
> https://packages.gentoo.org/packages/sys-libs/glibc
> 
> Same error regardless of the version of glibc I attempt to emerge.

Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't do 
that.

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/10/2018 01:53 PM, Nikos Chantziaras wrote:
> On 10/01/18 19:55, Corbin Bird wrote:
>> Is anyone else having a sys-libs/glibc emerge compile failure?
>>
>>> checking for python3... python3
>>> checking LD_LIBRARY_PATH variable... contains current directory
>>> configure: error:
>>> *** LD_LIBRARY_PATH shouldn't contain the current directory when
>>> *** building glibc. Please change the environment variable
>>> *** and run configure again.
>>>   * ERROR: sys-libs/glibc-2.25-r10::gentoo failed (configure phase):
>>>   *   failed to configure glibc
>>
>> sys-libs/glibc-2.25-r9 was set to masked / prompting this upgrade /
>> re-compile:
>>
>> https://packages.gentoo.org/packages/sys-libs/glibc
>>
>> Same error regardless of the version of glibc I attempt to emerge.
>
> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
> do that.
>
>

Unfortunately, I had to ( and didn't realize the implications. )
In .bashrc :
> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH

Required by the Vulkan Loader ( Mesa && Chromium ).

Corbin

[gentoo-user] Re: glibc emerge error

[Nikos Chantziaras]

On 11/01/18 15:28, Corbin Bird wrote:
>> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
>> do that.
> 
> Unfortunately, I had to ( and didn't realize the implications. )
> In .bashrc :
>> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
> 
> Required by the Vulkan Loader ( Mesa && Chromium ).

I think this is what the /etc/ld.so.conf.d/ directory is there for. Have 
you tried something like this instead:

   echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf
   env-update

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/11/2018 08:29 AM, Nikos Chantziaras wrote:
> On 11/01/18 15:28, Corbin Bird wrote:
>>> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
>>> do that.
>>
>> Unfortunately, I had to ( and didn't realize the implications. )
>> In .bashrc :
>>> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
>>
>> Required by the Vulkan Loader ( Mesa && Chromium ).
>
> I think this is what the /etc/ld.so.conf.d/ directory is there for.
> Have you tried something like this instead:
>
>   echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf
>   env-update
>
>

Will try this method and see what happens.

Checked a file already there. In the "05gcc-x86_64-pc-linux-gnu.conf"
there were no $PATH variables.
Put explicit paths in instead.

This will be interesting.

Corbin

[gentoo-user] Re: glibc emerge error

[Nikos Chantziaras]

On 12/01/18 18:31, Corbin Bird wrote:
> On 01/11/2018 08:29 AM, Nikos Chantziaras wrote:
>> On 11/01/18 15:28, Corbin Bird wrote:
>>>> Why are you setting LD_LIBRARY_PATH system-wide to begin with? Don't
>>>> do that.
>>>
>>> Unfortunately, I had to ( and didn't realize the implications. )
>>> In .bashrc :
>>>> export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH
>>>
>>> Required by the Vulkan Loader ( Mesa && Chromium ).
>>
>> I think this is what the /etc/ld.so.conf.d/ directory is there for.
>> Have you tried something like this instead:
>>
>>    echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf
>>    env-update
>>
> 
> Will try this method and see what happens.
> 
> Checked a file already there. In the "05gcc-x86_64-pc-linux-gnu.conf"
> there were no $PATH variables.
> Put explicit paths in instead.
> 
> This will be interesting.

Yes, you do add explicit paths in it. This:

   echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf

will write an explicit path (the variable is expanded by the shell.)

Re: [gentoo-user] Re: glibc emerge error

[Corbin Bird]

On 01/12/2018 04:14 PM, Nikos Chantziaras wrote:
> echo "$VULKAN_SDK/lib" > /etc/ld.so.conf.d/vulkan-loader.conf 

Found out what was giving me an extra slash in the output "...x86_64//lib"
The $VULKAN_SDK PATH had a slash at the end.

Works now. Thank you.

Corbin

[gentoo-user] Re: glibc emerge error

[Ian Zimmerman]

On 2018-01-11 07:28, Corbin Bird wrote:

> > export LD_LIBRARY_PATH=$VULKAN_SDK/lib:$LD_LIBRARY_PATH

This is wrong, because it will put the current directory (as represented
by the empty string) into the list even if it wasn't there originally.

Try something like this (untested):

export LD_LIBRARY_PATH=$VULKAN_SDK/lib${LD_LIBRARY_PATH:+":$LD_LIBRARY_PATH"}

see man bash, "Parameter expansion".

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.