Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 138650
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 133671
Assigned To: Gentoo Linux bug wranglers <bug-wranglers@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Drake Wyrm <lilwyrm@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
config.log requested config.log text/plain Drake Wyrm 2006-06-30 19:58 0000 34.85 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 138650 depends on: Show dependency tree
Bug 138650 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-06-30 19:55 0000
I came across this odd error while upgrading to the modular X. The
x11-libs/libXt-1.0.2 ebuild specifies x11-proto/kbproto as a DEPEND and
RDEPEND, but portage didn't merge that first. Consequently, I got the following
error:

<snip>
checking how to hardcode library paths into programs... immediate
checking for i686-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for XT... configure: error: Package requirements (sm x11 xproto
kbproto) were not met:

No package 'x11' found
No package 'kbproto' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XT_CFLAGS
and XT_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/libXt-1.0.2/work/libXt-1.0.2/config.log
<snip>

I am using sys-apps/portage-2.1-r1. Per the printed request from the ebuild, I
will attach the config.log. I am also going to install x11-proto/kbproto and
try again.

------- Comment #1 From Drake Wyrm 2006-06-30 19:58:43 0000 -------
Created an attachment (id=90582) [details]
requested config.log

------- Comment #2 From David ac 2006-06-30 23:17:45 0000 -------
hey

same issue here. I'd strongly suggest however that you change the component
field you selected from "core system" to "ebuilds" as core system should only
be used for sys-* package issues and there's much more chance that someone will
look at this issue if its under the ebuild component.

david

------- Comment #3 From Jakub Moc (RETIRED) 2006-06-30 23:27:59 0000 -------

*** This bug has been marked as a duplicate of 133671 ***

------- Comment #4 From David ac 2006-07-01 00:33:54 0000 -------
ok. well, i don't see how this is a duplicate of the other bug - isn't the
other one about the xterm ebuild? - nor do I see how the bugs been resolved.
I've re-synced my tree, and get exactly the same error.

interestingly when I do an emerge -uDNvp libXt I get a different set of
dependencies to be merged. getting sick of not having X to use, so i think I'm
just going to try a --oneshot merge on libXt to get the danm thing installed. 

Theres still a bug here though.

------- Comment #5 From Jakub Moc (RETIRED) 2006-07-01 00:39:25 0000 -------
(In reply to comment #4)
> ok. well, i don't see how this is a duplicate of the other bug - isn't the
> other one about the xterm ebuild? 

No, the bug is about missing deps that are not missing in fact; libXt depends
on x11-proto/kbproto, read the ebuild.

> just going to try a --oneshot merge on libXt to get the danm thing installed. 

emerge -1 x11-proto/kbproto would be better ;)

------- Comment #6 From Jakub Moc (RETIRED) 2006-07-02 03:35:57 0000 -------
*** Bug 138827 has been marked as a duplicate of this bug. ***

------- Comment #7 From Jakub Moc (RETIRED) 2006-07-28 10:09:20 0000 -------
*** Bug 142019 has been marked as a duplicate of this bug. ***

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug