Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 38596
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: SpanKY <vapier@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Allen Parker <infowolfe@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
emerge_info An output of emerge info text/plain Renzo 2004-02-11 09:38 0000 1.36 KB Details
config.log config.log of eterm merge text/plain Renzo 2004-02-11 21:46 0000 26.31 KB Details
ldd_usr_lib_libast_so ldd /usr/lib/libast.so text/plain Renzo 2004-02-11 23:46 0000 660 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 38596 depends on: Show dependency tree
Bug 38596 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: 2004-01-18 06:09 0000 
checking for libast-config... libast-config
checking for libast_malloc in -last... no

libast-config --version outputs 0.5
running kernel 2.6.1 (vanilla)
ACCEPT_KEYWORDS undefined

Reproducible: Always
Steps to Reproduce:
1. emerge eterm




Expected Results:  
eterm installs without error?

------- Comment #1 From SpanKY 2004-01-21 17:08:45 0000 ------- 
uhh, can you post the config.log from the build directory and `emerge info`

and so theres no confusion ... you installed via emerge or yourself ?

------- Comment #2 From Renzo 2004-02-11 09:38:49 0000 ------- 
Created an attachment (id=25418) [details]
An output of emerge info

I also get the errorr and have libast 0.5-r1 installed. It says that I may not
have it installed, or have it installed in a custom directory.

I don't know where config.log is located in the ebuild directory (I checked
x11-terms/eterm and couldn't find a log file). Any other information I can
provide?

------- Comment #3 From SpanKY 2004-02-11 17:43:34 0000 ------- 
/var/tmp/portage/eterm-0.9.2-r5/work/

the config.log file is in there somewhere

------- Comment #4 From Renzo 2004-02-11 21:46:56 0000 ------- 
Created an attachment (id=25455) [details]
config.log of eterm merge

If you need to know anything else, just ask.

------- Comment #5 From SpanKY 2004-02-11 21:58:50 0000 ------- 
/usr/lib/libast.so: undefined reference to `imlib_free_pixmap_and_mask'

what if you re-emerge libast and then try to emerge Eterm ?

if that doesnt work, what versions of imlib and imlib2 do you have on your system ?  what does `ldd /usr/lib/libast.so` show ?

------- Comment #6 From Renzo 2004-02-11 23:46:02 0000 ------- 
Created an attachment (id=25460) [details]
ldd /usr/lib/libast.so

Re-merging didn't work.

imlib: Not installed
imlib2: 1.1.0

Check attachment.

------- Comment #7 From SpanKY 2004-02-22 16:16:00 0000 ------- 
ah, it's /kind of/ your fault :)

emerging imlib2 with USE=-X causes this problem ... i'll put some logic into the libast ebuild to catch this

------- Comment #8 From SpanKY 2004-02-22 16:44:28 0000 ------- 
ok, libast-0.5-r2 fixes this

please upgrade to it

------- Comment #9 From SpanKY 2004-02-22 16:45:25 0000 ------- 
*** Bug 39687 has been marked as a duplicate of this bug. ***

------- Comment #10 From SpanKY 2004-03-24 12:10:27 0000 ------- 
*** Bug 45519 has been marked as a duplicate of this bug. ***

------- Comment #11 From Loki 2004-05-21 05:03:12 0000 ------- 
I still have the exact same error as the first guy even though i have libast
0.5-r2. i'm running kernel 2.6.5 gentoo-dev, stable keywords, on an athlon-xp

------- Comment #12 From SpanKY 2004-06-21 05:35:29 0000 ------- 
*** Bug 54593 has been marked as a duplicate of this bug. ***

------- Comment #13 From SpanKY 2004-09-01 06:26:30 0000 ------- 
*** Bug 62466 has been marked as a duplicate of this bug. ***

------- Comment #14 From SpanKY 2005-04-24 07:51:31 0000 ------- 
*** Bug 90206 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